Forum Replies Created
-
AuthorPosts
-
puxuradude6
ParticipantGot the same error, don’t even use AD but NTLMv2 on OS X Server seems to be incompatibel with the world anyway. I adjusted my share settings to allow NTLM as well and things worked from there on.
10.4.10 without AD or Kerberos, just local authentication.
puxuradude6
ParticipantI agree with you on that but this is a private network for a customer with a big house and lots of gear 🙂 In the meantime I’ve submitted the issue to 3com. In their knowledgebase was soomething that referred to the default setting of IGMP snooping that had to be enabled in order for mDNS to work. Haven’t got time to try it out but will keep you up to date.
Thanks for the feedback.
puxuradude6
ParticipantYou are correct, you have to open ports 3282 and 5900. However the way you are entering this in the firewall is all wrong. I wrote the correct (simplified) rules below:
allow tcp from <your ip> 5900 to any out
allow tcp from any to <your ip> 5900 inSo no UDP ports as they are not used. In the first rule you fill in your IP address at the source and the port number as well. The IP address at the destination is any and the port is empty. For the second rule it’s the other way around. Leave the source part to any and fill in the destination path.
You can do the same with port 3282 althoug if you’re using Mac OS X Server this port can be opened by selecting it in Apple’s GUI.
February 28, 2005 at 2:37 pm in reply to: rotatelog on OS X Server (Archive every 7 days)(awstats makes my head ache) #360857puxuradude6
ParticipantSince noone is commenting on your problem I’ll throw in my thoughts.
What I found out by reading the daily.out log file from the periodic program that apple runs with cron is that it does rotate the log files at that time which is 3.15. I set the server admin to rotate the logs once a day since I can’t figure out how to do the calculations otherwise. The log file my OS X server creates is names access.log.[numbers of seconds from 1970]. If you set the log file to rotate every week you’ll see that the next day awstats increases the number of seconds, therefore missing the log files. I tried doing a calculation using the day variable but awstats can’t handle those so I’m out of luck.
I now added a cron task that reads my access.log.[insert crappy second counting here] 5 minutes before the log is rotated and will see and wait if this works out.
I am really curious how the guys fmro afp548 set this up themselves. There are no tutorials online, neither can you find *any* examples of the config file online. Awstats themselves seem pretty ignorant about it as well. They added the seconds counting (which is obviously only for mac) as a variable but give no examples or references about how to use it properly in an OS X server environment.
I’ll get back to you about how my little cron job is doing, realising I’m missing 5 minutes of logs every day but I guess you can’t risk awstats reading the log file while OS X is deleting it…
February 28, 2005 at 2:37 pm in reply to: rotatelog on OS X Server (Archive every 7 days)(awstats makes my head ache) #360856puxuradude6
ParticipantSince noone is commenting on your problem I’ll throw in my thoughts.
What I found out by reading the daily.out log file from the periodic program that apple runs with cron is that it does rotate the log files at that time which is 3.15. I set the server admin to rotate the logs once a day since I can’t figure out how to do the calculations otherwise. The log file my OS X server creates is names access.log.[numbers of seconds from 1970]. If you set the log file to rotate every week you’ll see that the next day awstats increases the number of seconds, therefore missing the log files. I tried doing a calculation using the day variable but awstats can’t handle those so I’m out of luck.
I now added a cron task that reads my access.log.[insert crappy second counting here] 5 minutes before the log is rotated and will see and wait if this works out.
I am really curious how the guys fmro afp548 set this up themselves. There are no tutorials online, neither can you find *any* examples of the config file online. Awstats themselves seem pretty ignorant about it as well. They added the seconds counting (which is obviously only for mac) as a variable but give no examples or references about how to use it properly in an OS X server environment.
I’ll get back to you about how my little cron job is doing, realising I’m missing 5 minutes of logs every day but I guess you can’t risk awstats reading the log file while OS X is deleting it…
-
AuthorPosts
Recent Comments