rdlugosz.10120601@bloglines.com
2005-May-12 23:23 UTC
[Instiki] Instiki not writing snapshots?
Lately my instiki hasn''t been outputting any snapshots to the storage directory. I''m running 0.10.1 and the only "strange" thing about my setup is that I''ve imported the content via the (production disabled) /import action that I''ve discussed in other threads here. I''ve got an ever-growing 00...01.command_log file, but there are *no* snapshot files! I guess this probably isn''t the end of the world, presuming Instiki will restart correctly should I bounce it, but something doesn''t seem right. Any thoughts?
rdlugosz.10120601@bloglines.com wrote:>I''ve got an ever-growing 00...01.command_log >file, but there are *no* snapshot files! I guess this probably isn''t the >end of the world, presuming Instiki will restart correctly should I bounce >it, but something doesn''t seem right. Any thoughts? > >The thread responsible for taking snapshots is in wiki_service.rb, start_snapshot_thread method. It will always try to write a snapshot on startup, if there is a command.log; if it cannot (for whatever reason), it should log an error (including full stack trace) in stderr. Please try to run instiki from command line, without --daemon option, and see what it has to say. -- Best regards, Alexey Verkhovsky Ruby Forum: http://ruby-forum.org (moderator) RForum: http://rforum.andreas-s.net (co-author) Instiki: http://instiki.org (maintainer)
Alexey et al
I see this behavior as well on Mac OS X Server 10.3. I get very
strange snapshot schedules that seem to stop after the first snapshot:
drwxr-xr-x 25 myuser myuser 850 23 May 19:06 .
drwxr-xr-x 3 myuser myuser 102 12 May 05:36 ..
-rw-rw-rw- 1 myuser myuser 1153232 22 May 18:23
000000000000000000001.command_log
-rw-r--r-- 1 myuser myuser 2032 11 May 18:16
000000000000000000001.snapshot
-rw-r--r-- 1 myuser myuser 5177 11 May 18:16
000000000000000000002.snapshot
-rw-r--r-- 1 myuser myuser 6219 11 May 18:16
000000000000000000003.snapshot
-rw-r--r-- 1 myuser myuser 8450 11 May 18:16
000000000000000000004.snapshot
-rw-r--r-- 1 myuser myuser 9085 11 May 18:16
000000000000000000005.snapshot
-rw-r--r-- 1 myuser myuser 9682 11 May 18:16
000000000000000000006.snapshot
-rw-r--r-- 1 myuser myuser 9973 11 May 18:16
000000000000000000007.snapshot
-rw-r--r-- 1 myuser myuser 11001 11 May 18:16
000000000000000000008.snapshot
-rw-r--r-- 1 myuser myuser 12485 11 May 18:16
000000000000000000009.snapshot
-rw-r--r-- 1 myuser myuser 12717 11 May 18:16
000000000000000000010.snapshot
-rw-r--r-- 1 myuser myuser 12701 11 May 18:16
000000000000000000011.snapshot
-rw-r--r-- 1 myuser myuser 79400 11 May 18:16
000000000000000000012.snapshot
-rw-r--r-- 1 myuser myuser 81774 11 May 18:24
000000000000000000013.snapshot
-rw-r--r-- 1 myuser myuser 94442 11 May 19:24
000000000000000000014.snapshot
-rw-r--r-- 1 myuser myuser 95895 11 May 20:24
000000000000000000015.snapshot
-rw-r--r-- 1 myuser myuser 100655 11 May 21:24
000000000000000000016.snapshot
-rw-r--r-- 1 myuser myuser 105795 11 May 22:24
000000000000000000017.snapshot
-rw-r--r-- 1 myuser myuser 106570 11 May 23:24
000000000000000000018.snapshot
-rw-r--r-- 1 myuser myuser 107239 12 May 00:24
000000000000000000019.snapshot
-rw-r--r-- 1 myuser myuser 108299 12 May 01:24
000000000000000000020.snapshot
That listed ran just now on May 23. Note when the snapshots stop and
the size and date of the command_log. You can also see that the
snapshots may correspond with the start of the daemon:
thomassmith:~/daemons/instipackage/instiki-0.10.1 myuser$ ps -uxM
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME PRI
STIME UTIME COMMAND
myuser 18444 0.0 0.1 27552 532 ?? S 8May05 0:00.00 31
0:00.00 0:00.00 tim
myuser 18745 0.0 5.5 66128 28656 ?? S 12May05 12:34.64 31
1:05.38 11:29.26 ruby/bin/ruby -I
/Users/myuser/daemons/instipackage/ruby
myuser 27701 0.0 0.1 30740 448 ?? S 9:26PM 0:00.43 31
0:00.25 0:00.18 /usr/sbin/sshd -i
myuser 27702 0.0 0.2 18644 816 std S 9:26PM 0:00.37 31
0:00.30 0:00.07 -bash
Hard to read in the above, but it shows the Instiki process starting at
about the time of the last two snapshots, making it appear that Instiki
started, wrote a snapshot via the snapshot thread an hour later, then
lost the snapshot thread. Note that running ps with the -M switch
should show additional threads for the processes, if any. In this
case, we only see one thread - the main thread, for the ruby process.
I''ll add this up to the bug report system, but wanted to run this by
people first. This is a 0.10.1, but the webs running at 0.10.0.
Tam?s
On May 12, 2005, at 11:48 PM, Alexey Verkhovsky wrote:
rdlugosz.10120601@bloglines.com wrote:
> I''ve got an ever-growing 00...01.command_log
> file, but there are *no* snapshot files! I guess this probably
isn''t
> the
> end of the world, presuming Instiki will restart correctly should I
> bounce
> it, but something doesn''t seem right. Any thoughts?
>
The thread responsible for taking snapshots is in wiki_service.rb,
start_snapshot_thread method.
It will always try to write a snapshot on startup, if there is a
command.log; if it cannot (for whatever reason), it should log an error
(including full stack trace) in stderr.
Please try to run instiki from command line, without --daemon option,
and see what it has to say.
--
Best regards,
Alexey Verkhovsky
Ruby Forum: http://ruby-forum.org (moderator)
RForum: http://rforum.andreas-s.net (co-author)
Instiki: http://instiki.org (maintainer)
_______________________________________________
Instiki-users mailing list
Instiki-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/instiki-users
Tam?s Smith wrote:> Note that running ps with the -M switch should show additional threads > for the processes, if any. In this case, we only see one thread - the > main thread, for the ruby process.Ruby threads are green threads - Ruby is not using native OS threads. So, if you do something like ruby -e ''10.times { Thread.new { sleep 1000 } }'', you won''t see multiple threads either. -- Best regards, Alexey Verkhovsky Ruby Forum: http://ruby-forum.org (moderator) RForum: http://rforum.andreas-s.net (co-author) Instiki: http://instiki.org (maintainer)