[TvE]

[QUOTE][u]Quote by: impax[/u][p]
We are looking to hire someone to take a look at our server and get timsieved working. Our server is in production and we would require that you work on the server in the evening after 6pm PST.

If you are interested please contact me directly.

Thanks
-Joe Crain
[/p][/QUOTE]

Then I would reccommend to take a look at [url]http://osx.topicdesk.com[/url] They look extremely suited for a job just like yours

[TvE]

Yes upgrade to a newer version of SM

I am in the process of testing this (with SM 1.4.10a) on my test-server (that’s why I saw this post – I had the same error ;-).

Read this guide [url]http://squirrelmail.org/docs/admin/admin-4.html[/url]
and remember that SM lives in [b]/usr/share[/b] and that the default OS X ownership are [b]root:wheel[/b]

I think that was the only differences I found!

[TvE]

Perhaps you have upgradeed the server to PHP5?

[TvE]

For those of you fancy some security and who do not want to enable PLAIN can find a desciption of the solution here: [url]http://discussions.apple.com/thread.jspa?threadID=131554&start=25&tstart=0[/url] where “tknospdr” writes:
————————————–
Posted: Jun 24, 2006 12:29 AM in response to: tknospdr

I answered my own question by finally taking the time to read the config.php file myself.
If you want your webmail to be a bit more secure and don’t want to enable plain or clear…

Change line 48 in config.php from:
$sieve_preferred_sasl_mech = ‘PLAIN’;

to
$sieve_preferred_sasl_mech = ‘PLAIN CRAM-MD5’;

That’s it, now you can sleep better at night, well at least I can anyway.
————————————–

This was the one bit of information I was missing before I wanted to install it on my server 🙂

[TvE]

As written from you on the OS X Server mailing list on november 30’th:
[quote]All in all, its a strange problem. I’ll see if the script I added to daily
to restart the syslogd works to continue the logging then perhaps we can see
what is affecting amavis.[/quote]

What was the result of this?

😉 TvE

[TvE]

[QUOTE][u]Quote by: wpd7[/u]

In the periodic/daily scripts, what does the number in front of the filename mean? I’m assuming these are times? If so, I am contemplating putting in a 320.daily-reboot file with a restart script for the time being to reduce our blacklist placement (due to SPAMS being forwarded) and also reduce our SPAM overall.[/QUOTE]

I doubt that it will be times, the time is controlled by CRON (or perhaps it’s now launchd) – I’d think that it’s there to generate the *order* that the scripts is being executed at.
Take a look at man periodic and you’ll see:

“The periodic program will run each executable file in the directory or directories specified. If a file does not have the executable bit set, it is silently ignored”

I think that (for the daily scripts) first is the 100.… executed, then the 500.…
AND if you make your 320.x it’ss be executed in between the two

[code]TvE-iMac24:~ tve$ ls -l /etc/periodic/daily/
total 16
-r-xr-xr-x 1 root wheel 1389 Jul 2 02:15 100.clean-logs
-r-xr-xr-x 1 root wheel 3964 Jul 2 02:15 500.daily[/code]

[QUOTE]If you can point out to me where I should be looking for possible malicious software or code, that would be greatly appreciated!

[/QUOTE]

Hmm – take a look at http://FilthyCodersFilthyWebsiteWithBadCode.gone
(or do you mean on your local drive ;-P)

[TvE]

[QUOTE][u]Quote by: wpd7[/u]

TvE- I was beginning to think that I’m the only one here…

Unfortunately your theory about 10.4.8 is inaccurate- I am currently running 10.4.8! 😕 [/QUOTE]
Theory not quite, but possibility yes 😉
[QUOTE]I have been rebooting the machine daily as I come in – I find that’s the best way to get everything up and running again- stopping and starting the mail service is not reliable as most of the time it will not start up alk the services correctly.

[/QUOTE]
Hmm – to me that indicates other problems that I (so far) have not seen at all on “my” servers.
I would be digging my logs to see WHY I would be unable to have all the mailservice relaunched.
What you’re doing at the moment is just massaging the symptoms, not trying to find (and eliminate) the cause of the problem…

[TvE]

[QUOTE][u]Quote by: MacTroll[/u]

Happening dailiy at 3:15 is quite bizarre. You check your cron tab and the periodic scripts to see if something has been added?

[/QUOTE]
I have recently ALSO seen this behavior on several 10.4.x servers.

EG. one of the servers (running 10.4.7, also on november 26’th) shows this:
-rw-r—– 1 clamav admin 0 Nov 26 03:15 amavis.log
-rw-r—– 1 clamav admin 127513 Nov 26 02:47 amavis.log.0.gz
-rw-r—– 1 clamav admin 71688 Nov 12 03:12 amavis.log.1.gz
-rw-r—– 1 clamav admin 243525 Oct 22 03:15 amavis.log.2.gz
-rw-r—– 1 clamav admin 3831502 Oct 8 03:15 amavis.log.3.gz
-rw-r—– 1 clamav admin 2653546 Aug 27 03:14 amavis.log.4.gz

So I think the problem was introduced with the 10.4.7 update.

I have not yet applied the latest Security Update (that updates amavis) or 10.4.8… Those might change the problem!

I also

[TvE]

This does not sound like any kind of OS X specific problem, but a general DNS (or perhaps a router) problem.

[TvE]

I am also on the way to begin using the “RAID-1 (mirror) with a third disk as backup” type of solution.

My idea is to “break” the mirror and take disk # 3 offsite for disaster recovery.
This solution sounds a lotbetter than a cp-cronjob.
I doubdt that it can be many ressources that are used to write (the same) data to one more disk – if that’s the case a faster server might be required anyways…

[TvE]

[QUOTE][u]Quote by: filipp[/u]

Indeed, the sorting seems to be totally crazy. If you look closer, it’s never actually really sorted by anything. The results just sort start off OK, but then at some point lose the ordering.
Thanks for noticing!
Will investigate…

[/QUOTE]

Only happy to be able to help 😉

[TvE]

Which was easy:
logresolvemerge.pl needs a fix on line 87:
From: my $zcat = ‘zcat’;
To: my $zcat = ‘gzcat’;
Reason is explained here: [url]http://www.osxfaq.com/tips/unix-tricks/week106/monday.ws[/url]

[TvE]

Hmm – according to this very interesting post: https://sourceforge.net/forum/message.php?msg_id=3518899 if you “just” change the line endings from DOS to UNIX on logresolvemerge.pl it solves the problem (good error description ;-P)

Now the output of my command is totally different:
[quote]testserver:/usr/local/awstats/tools ladmin$ sudo /usr/local/awstats/tools/awstats_updateall.pl now
Running ‘”/usr/local/awstats/wwwroot/cgi-bin/awstats.pl” -update -config=testserver -configdir=”/usr/local/awstats/wwwroot/cgi-bin”‘ to update config testserver
Update for config “/usr/local/awstats/wwwroot/cgi-bin/awstats.testserver.conf”
With data in log file “/usr/local/awstats/tools/logresolvemerge.pl /var/log/httpd/access_log.* |”…
zcat: /var/log/httpd/access_log.1150848000.gz.Z: No such file or directory
Phase 1 : First bypass old records, searching new record…
Direct access to last remembered record has fallen on another record.
So searching new records from beginning of log file…
Phase 2 : Now process new records (Flush history on disk after 20000 hosts)…
Jumped lines in file: 0
Parsed lines in file: 316
Found 0 dropped records,
Found 0 corrupted records,
Found 120 old records,
Found 196 new qualified records.

testserver:/usr/local/awstats/tools ladmin$ [/quote]

Now I just have to remember where I read the solution to the next problem:
zcat: /var/log/httpd/access_log.1150848000.gz.Z: No such file or directory

[TvE]

[QUOTE][u]Quote by: Ski Developer[/u]

Hello,

I’ve searched high and low and cannot find the answer to this simple problem.

Background:

I have migrated from Linux to Mac OS 10.4 Server running the stock Apache/PHP/Mysql setup.
I am virtual hosting a dozen web sites.

The problem:

I want to enable error_reporting for php. I have made the change in /private/etc/php.ini.

I have restarted web services and even rebotted the server since this change. How do I get
apache to read the php.ini file. Can I do it via command line…. and still utilize the Server Admin
tool….?

Thanks in Advance…

Michael

[/QUOTE]Is the file readable for user www?

[TvE]

[QUOTE][u]Quote by: macshome[/u]

We roll your logs weekly and retain one week of archive. We read them with the logresolvemerge.pl tool, which sorts and reads the logs. It’s in the tools dir of your awstats deployment. Your log directive in the config file then looks something like:

LogFile="/somepath/awstats/tools/logresolvemerge.pl /var/log/httpd/access_log.* |"

Or thereabouts.

[/QUOTE]

I must be missing something essential, since I am unable to get the above to wotk (I have corrected /somepath to a meaningfull path 😉

My error is:
[code]testserver:/var/log/httpd ladmin$ sudo /usr/local/awstats/tools/awstats_updateall.pl now
Password:
Running ‘”/usr/local/awstats/wwwroot/cgi-bin/awstats.pl” -update -config=testserver -configdir=”/usr/local/awstats/wwwroot/cgi-bin”‘ to update config testserver
Update for config “/usr/local/awstats/wwwroot/cgi-bin/awstats.testserver.conf”
With data in log file “/usr/local/awstats/tools/logresolvemerge.pl /var/log/httpd/access_log.* |”…
: bad interpreter: No such file or directory.pl: /usr/bin/perl
Phase 1 : First bypass old records, searching new record…
Direct access to last remembered record is out of file.
So searching it from beginning of log file…
Error: Command for pipe ‘/usr/local/awstats/tools/logresolvemerge.pl /var/log/httpd/access_log.* |’ failed
Setup (‘/usr/local/awstats/wwwroot/cgi-bin/awstats.testserver.conf’ file, web server or permissions) may be wrong.
Check config file, permissions and AWStats documentation (in ‘docs’ directory).
[/code]

AWStats have been installed (and is otherwise working) according to this nice article:
[url]https://www.afp548.com/article.php?story=20060823205258972[/url]

[Author]

Posts