I am currently running 5.0-rc4 and things are working fine except this one error.  The last time I booted up the server was on 6/17 and have been out of town since 6/18 but everything was left running for my family.  They joined me out of town a week later, of course someone was supposed to shut it down but didnt  . 

 

I just got back, everything is running fine, but looking at the syslog there is this error repeated every hour.

 

crond[1218]: ignoring /var/spool/cron/crontabs/root- (non-existent user)

 

It started right at 1 hour after the initial reboot and never quit. 

 

I also noted when I first looked at the server only two drives were spun down after 2 weeks of zero activity.  When I forced spindown, everything spundown as it should.

 

I am about to upgrade to 5.0-r5 but wanted to see if anyone else had either of these issues or if it was known?

 

My signature hardware configuration is current and syslog is attached. 

 

Any help is appreciated.

syslog-2012-07-06.txt

Remove Simplefeatures and the entry will cease.

Remove Simplefeatures and the entry will cease.

 

Just added my add-ons to my signature, not running simplefeatures.  Was considering adding it but haven't.

 

Also added my syslog, forgot to attach.

Disable all the add-ons to see if it goes away.

Disable all the add-ons to see if it goes away.

It is one of those added through unMENU most likely.

 

You can ignore the error. It is harmless.  It will not go away until you un-install the package that is using cron (and creating it), and then reboot.  (or, you can remove the file yourself)  Just add

rm /var/spool/cron/crontabs/root-

at the end of your config/go script.

 

You can also type the same command at the linux command prompt, to remove the file without rebooting.

rm /var/spool/cron/crontabs/root-

In older versions of unRAID, it expected the root- file to be there.  The newer releases stopped using it.

Disable all the add-ons to see if it goes away.

It is one of those added through unMENU most likely.

 

You can ignore the error. It is harmless.  It will not go away until you un-install the package that is using cron (and creating it), and then reboot.  (or, you can remove the file yourself)  Just add

rm /var/spool/cron/crontabs/root-

at the end of your config/go script.

 

You can also type the same command at the linux command prompt, to remove the file without rebooting.

rm /var/spool/cron/crontabs/root-

In older versions of unRAID, it expected the root- file to be there.  The newer releases stopped using it.

 

Thanks,

If I remove the file using the 2nd option is that permanent?  Can I still continue to use the same add-ons I have been using or will it start back up every time? 

 

If that is the case then by adding it to the go script do I solve it permanently, again without removing my add-ons?

 

Now that I just started a preclear for a replacement parity drive tonight I can't reboot till Sunday.  Installing my first 3TB drive for parity and keeping the older 2 TB as a warm spare. 

Disable all the add-ons to see if it goes away.

It is one of those added through unMENU most likely.

 

You can ignore the error. It is harmless.  It will not go away until you un-install the package that is using cron (and creating it), and then reboot.  (or, you can remove the file yourself)  Just add

rm /var/spool/cron/crontabs/root-

at the end of your config/go script.

 

You can also type the same command at the linux command prompt, to remove the file without rebooting.

rm /var/spool/cron/crontabs/root-

In older versions of unRAID, it expected the root- file to be there.  The newer releases stopped using it.

 

Thanks,

If I remove the file using the 2nd option is that permanent?

No, the file will be created again when the add-ons auto-re-install themselves the next time you reboot.

 

Therefore, you should do both.  Add the "rm" command to the end of the "config/go" script (you can use the "view/edit config files" built into unMENU to add the line to the "go" script) and then also type the same command at the linux prompt to remove the "root-" file now without rebooting.  That way you will not need to interrupt your prclearing.  There will be no need to reboot at all.

  Can I still continue to use the same add-ons I have been using or will it start back up every time? 

The current add-on(s) creating the "root-" file will recreate it every time they are installed (every time you reboot) therefore, adding that same "rm" command to the end of the "go" script will remove the "root-" file each time you reboot.

If that is the case then by adding it to the go script do I solve it permanently, again without removing my add-ons?

Correct.  but adding the line to the "go" script will not stop the messages until you reboot (and the "go" script is next invoked), therefore you can invoke the same "rm" command once by hand on the command line after you add it to the config/go file.  That will stop the error messages being logged until you next reboot.

Now that I just started a preclear for a replacement parity drive tonight I can't reboot till Sunday.  Installing my first 3TB drive for parity and keeping the older 2 TB as a warm spare.

Sounds fine.  You can add the entry in the config/go file now, and also invoke the "rm" command once on the linux command line, and between them the syslog error messages will no longer occur.

 

Joe L.

PS. I'm going to move this thread to the customizations forum, as it has nothing to do with rc5.

Problem solved, thanks all for the help.

 

Sorry for it landing in the wrong location initially, but hand't previously noted the error so was thinking it was r5 related.