Topic: WEIRD? or not..

[Peter Spencer]

Hi,

U have 2 x e-smith 5.6 boxes running.

they are at different locations, different in every way and till now I have never had an error message come through an email...

and then, last night while I was sleeping.. BOTH OF THEM sent me an email that said..

/etc/cron.daily/logrotate:

proftpd: no process killed
error running postrotate script

OK, I know it's just an error message - something about proftpd but WHY did they both come on same day! also, I have tried FTP'ing in and it works so ftpd seems still to be working..

many thanks!
PS

[Andrew Rosenau]

I also recieve that error message from my SME 5.6 server, and my FTP works fine--I've just ignored it. Would be interested to know if anyone knows what it means--it appears to me its just a problem with rotating the logs.

[Jan]

Yep... me 3. I have also gotten the same error message. Have no idea as to what causes it but all seems to continue to work fine. I'm hoping someone who knows what causes it or knows howto find out picks up this thread.

Regards,

Jan

[guestHH]

Anybody sent it to smebugs@mitel.com yet?

[Jan]

RequestedDeletion,

Ehmm no not really. I for one _did_ install several add-ons so I thought it could have been due to these contribs. Added to this, I don't think it causes any problems because all seems to work fine otherwise.

Since Peter told us here he did not add any contrib or changed anything exceptional, I suppose it'd be a good idea if he or someone else who also hasn't added stuff to send in the bug report. Or am I just diverting responsibility here?

If none will send it in I will do so next weekend.

Regards,

Jan

[Ray Mitchell]

If you all learn to search this forum you would find the answer.
Search on
"error running postrotate script"
including the " ", and for all dates, and look particularly at Damien Curtains post which explains it.

Regards
Ray

[Dave Liquorice]

> If you all learn to search this forum you would find the answer.

Well it does explain where the error orginates but it doesn't explain why it doesn't occur everytime the logrotate script is run. I've had it 3 times in the last couple of weeks.

DC>  Why this isnt  working is that proftpd is run via inetd, not as a
DC> standalone server. If it was a standalone server the above
DC> command would run fine, and proftpd would resume logging
DC> correctly after a logrotate has occurred.

Given that explantion I would expect the error every time as proftd wouldn't normally be there. The only vague pattern I can spot is that the error occurs some time after I have used FTP into the SME box. Something is back to front in the explanation.

Cheers
Dave.

[Ray Mitchell]

I was happy enough with the explanation.

I receive the message once a week every Sunday on 5.6U4 servers.

Regs
Ray

[Chris Gray]

I get this message regulary also, and have done since I installed the server Dec 2002.!   I just ignore it and the server works fine.  I have no contribs loaded either.