Topic: Cron message

[Orville Carter]

I am getting the following message from my e-smith 4.0 final server-gateway machine.

From: Cron Daemon
To: root@lxxxxxxxx.com

Subject: Cron run-parts /etc/cron.daily

error: bad line 19 in state file /var/lib/logrotate.status


The system works fine and all email is coming through. I got this message each day for the past 3 days.
Any ideas????

[Lars Thorelius]

I fetch our mail by multidrop from a POP account. When my ISP was down for technical reasons last week I got a root@... each time the connection to the POP account failed (68 e-mails!).

I understand that I get a notice about it. I never heard of Root as an administrative account though, I thought it was supposed to be Admin. Why is it Root?

(Sorry, I didn´t help you much with your question.)

Regards
Lars

[Orville Carter]

Lars,
We do the same for our multiple mail boxes, and all mail is delivered.
This message occurs at the same time every day (4:03am).
Yes, the root@lxxxxxxxx.com surprised me also. Mail delivery problems
always sent me messages at admin@lxxxxxxxx.com.

However, this does not appear to be email related.

This is the logrotate.status file: [line # added by me for clarity]

logrotate state -- version 1  [line 1]
/var/log/httpd/acces_log 200-8-4 [line 2]
...
...
...
...
/var/log/cron 2000-8-4  [line 16]
/var/log/wtmp 2000-8-4  [line 17]
/var/log/lastlog 2000-8-5  [line 18]
/var/log/samba/log.pii 466 2000-8-5 [line 19]
/var/log/samba/log.winstation4 2000-8-5   [line 20 - last line]

Winstation4 is one of my win98 systems on the lan. This pc clock is fine.
in fact, cmos clocks on all win98 machines are good. In line 19 the "pii 466"
is a mystery. All my win98 machines are called "winstationX". I may have
used the "pii 466" while configuring a clients' machine. But that was several weeks
back.

[Charlie Brady]

Lars Thorelius wrote:

> I understand that I get a notice about it. I never heard of
> Root as an administrative account though, I thought it was
> supposed to be Admin. Why is it Root?

The "root" account is the standard linux administrative account. The e-smith "admin" account is an administrative account with restricted powers, in line with the e-smith "reliable but as easy as possible" philosophy.

Regards

Charlie

[Lars Thorelius]

> The "root" account is the standard linux
> administrative account. The e-smith "admin" account
> is an administrative account with restricted powers, in line
> with the e-smith "reliable but as easy as possible"
> philosophy.


Of course. But working with e-smith I thought I was considered to be Admin, and I would like to get the messages of any e-mail-failures. Otherwise I guess I have to set up a Root user name as well, and I don´t find this in the dokumentation. Shouldn´t it be Admin for this kind of message after all?

Regards
Lars

[Charlie Brady]

Lars Thorelius wrote:

> > The "root" account is the standard linux
> > administrative account. The e-smith "admin" account
> > is an administrative account with restricted powers, in
> > line with the e-smith "reliable but as easy as
> > possible"  philosophy.
>
> Of course. But working with e-smith I thought I was considered
> to be Admin, and I would like to get the messages of any
> e-mail-failures. Otherwise I guess I have to set up a Root user
> name as well, and I don´t find this in the dokumentation.
> Shouldn´t it be Admin for this kind of message after all?

I don't understand your problem. You receive email messages which are sent by the "root" account. The messages are forwarded to the admin email address, presumably yours. You do not have to set up a root account. It already exists, but during normal operation you never have to use it for anything.

Regards

Charlie

[Hasan Muhammad]

Here's the fix:

Notice the line number

   error: bad line 19 in state file /var/lib/logrotate.status

Edit /var/lib/logrotate.status
  - go to that line number
  - Note the name of the Windows machine listed on that line (the name will include an embedded space--which is the source of the problem).

Go to the /var/log/samba directory and remove the file associated with that machine name (and remove the files for any other Windows machines with an embedded space in the name).

Remove the /var/lib/logrotate.status file.

Go to every Windows machine whose name includes an embedded space:
   - rename the machine (Control Panel/Network/Identification/Computer Name)
   - reboot the computer

That should fix the problem.

Hasan

[Charlie Brady]

Orville Carter wrote:

> I am getting the following message from my e-smith 4.0 final
> server-gateway machine.
>
> From: Cron Daemon To: root@lxxxxxxxx.com
>
> Subject: Cron run-parts /etc/cron.daily
>
> error: bad line 19 in state file /var/lib/logrotate.status
>
>
> The system works fine and all email is coming through. I got
> this message each day for the past 3 days. Any ideas????

See my followup at:

http://www2.e-smith.net/bboard/read.php3?num=1&id=3242&thread=2891

Regards

Charlie