Re: [OpenIndiana-discuss] log messages from failed time-slider daemon
James Carlson writes: >> What is going on that requires crontab to be read? And what might make >> it not open.. permissions? > > The script this service runs modifies crontab entries (yecch!). Not > opening could be due to user modification of the time-slider service > itself, bad permissions somewhere, or a read-only file system. I forgot to mention this: In the gui I started the timeslider and it appeared to be off by default so I checked the `enable' box. Next bootup is when I first noticed the failures. So unless checking `enable' counts as a user modification then there should be none. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] log messages from failed time-slider daemon
James Carlson writes: > On 10/27/11 18:34, Harry Putnam wrote: >> Note that top line about `crontab'. Is that the reason for the >> subsequent failures? > > It appears to be. > >> What is going on that requires crontab to be read? And what might make >> it not open.. permissions? > > The script this service runs modifies crontab entries (yecch!). Not > opening could be due to user modification of the time-slider service > itself, bad permissions somewhere, or a read-only file system. > > Try: > > ls -ld /var/spool/cron/crontabs > df /var/spool/cron/crontabs > # ls -ld cron drwxr-xr-x 4 root sys 4 2011-09-12 06:47 cron ---- ---=--- - # ls -ld cron/crontabs drwxr-xr-x 2 root sys 7 2011-10-28 22:13 cron/crontabs ---- ---=--- - # df /var/spool/cron/crontabs Filesystem 1K-blocks Used Available Use% Mounted on rpool/ROOT/openindiana 27524993 16362570 11162423 60% / ---- ---=--- - # /bin/df /var/spool/cron/crontabs / (rpool/ROOT/openindiana):22324845 blocks 22324845 files ---- ---=--- - # crontab -l > newcrontab # crontab newcrontab (no errors or warnings) To my inexperienced eye, this all looks pretty normal... is it? ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] log messages from failed time-slider daemon
On 10/27/11 18:34, Harry Putnam wrote: > Note that top line about `crontab'. Is that the reason for the > subsequent failures? It appears to be. > What is going on that requires crontab to be read? And what might make > it not open.. permissions? The script this service runs modifies crontab entries (yecch!). Not opening could be due to user modification of the time-slider service itself, bad permissions somewhere, or a read-only file system. Try: ls -ld /var/spool/cron/crontabs df /var/spool/cron/crontabs > Is this the root crontab, or would it be a user crontab?... there is > so little information in the log output its not really possible to > figure much from it. It looks like the root crontab. Something is definitely strange on your system. If you do this: pfexec su - root crontab -l > /tmp/root.cron crontab /tmp/root.cron what happens? -- James Carlson 42.703N 71.076W ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] log messages from failed time-slider daemon
I've been told that the time-slider does not work on 151 but also
several posters responded that it works fine for them. I'm hoping I
can get it to work too, but not sure where to start.
application/time-slider:default fails during boot up. When I look at
the log I see it attempting to start over and over and finally giving
up.
---- ---=--- -
[...]
[ Oct 21 14:03:52 Executing start method ("/lib/svc/method/time-slider start").
]
crontab: can't open your crontab file.
[ Oct 21 14:04:53 Method or service exit timed out. Killing contract 117. ]
[ Oct 21 14:04:53 Method "start" failed due to signal KILL. ]
[ Oct 21 14:04:53 Executing start method ("/lib/svc/method/time-slider start").
]
[ Oct 21 14:05:54 Method or service exit timed out. Killing contract 118. ]
[ Oct 21 14:05:54 Method "start" failed due to signal KILL. ]
[ Oct 21 14:05:55 Executing start method ("/lib/svc/method/time-slider
start").
[...]
---- ---=--- -
Note that top line about `crontab'. Is that the reason for the
subsequent failures?
What is going on that requires crontab to be read? And what might make
it not open.. permissions?
Is this the root crontab, or would it be a user crontab?... there is
so little information in the log output its not really possible to
figure much from it.
Do I need to increase verbosity somewhere to get usable information?
Maybe the output is plenty for an experienced system administrator but
for us regular doodoos its a bit sparse.
Looking at /var/spool/cron/crontabs
-rw--- 1 root sys1004 2011-09-12 06:47 adm
-r 1 root root 1365 2011-09-12 06:47 lp
-rw--- 1 root root 1241 2011-10-27 16:09 root
-rw--- 1 root sys1122 2011-09-12 06:47 sys
-rw--- 1 root daemon0 2011-10-27 16:12 zfssnap
The only one that would be un-writable to root is `lp' and I'm pretty
sure that is not involved here
So anyway, can anyone tell what is going on in the log? Or in the
included screenshot of the boot messages:
<>___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
