Issues - mojombo/god

mojombo / god

438

Description:

Ruby process monitor

Sort by: Priority | Votes | Last Updated

Loading…

1.

0 votes

The server is not available (or you do not have permissions to access it)
1 comment Created 6 months ago by gdi

Title

Body
We see this error about 1/3rd of the time when trying to restart god (after, say, disabling it via god terminate); all god commands save 'god check' will report this. What are some of the causes of this error? We also see instances where a watch with both a :process_running and a :cpu_usage condition will fail to restart a process which is no longer running. Checking the god log for that watch, we see a large list of successful status checks for cpu usage -- 0%, naturally. Are we missing some basic permissions issue here? God is running as root, so it seems unlikely, but...
or cancel

We see this error about 1/3rd of the time when trying to restart god (after, say, disabling it via god terminate); all god commands save 'god check' will report this. What are some of the causes of this error?

We also see instances where a watch with both a :process_running and a :cpu_usage condition will fail to restart a process which is no longer running. Checking the god log for that watch, we see a large list of successful status checks for cpu usage -- 0%, naturally.

Are we missing some basic permissions issue here? God is running as root, so it seems unlikely, but...

Comments

mojombo Sun Aug 09 13:21:33 -0700 2009 | link

What command are you using to restart god? That error occurs when the god daemon isn't running or the user under which you're running the god query does not have permission to the socket file which is owned by the process that was used to start god.

Can you split the other question into a separate ticket, doubling up tickets like this makes things difficult to track and address.

Comment
What command are you using to restart god? That error occurs when the god daemon isn't running or the user under which you're running the god query does not have permission to the socket file which is owned by the process that was used to start god. Can you split the other question into a separate ticket, doubling up tickets like this makes things difficult to track and address.
or cancel

Parsed with GitHub Flavored Markdown
2.

1 vote

Twitter gem has changed
1 comment Created 5 months ago by myobie

Title

Body
Instead of Twitter::Base.new(username, password) you have to build a Twitter::HTTPAuth.new('username', 'password') first. I am willing to submit a patch, but I am not sure if backward compatibility with the old twitter gem is necessary?
or cancel

Instead of Twitter::Base.new(username, password) you have to build a Twitter::HTTPAuth.new('username', 'password') first. I am willing to submit a patch, but I am not sure if backward compatibility with the old twitter gem is necessary?

Comments

mojombo Sun Aug 09 13:23:19 -0700 2009 | link

It would be best to maintain backwards compatibility for a while and add a deprecation notice to the documentation. Sometime down the road we can then remove support for the old gem.

Comment
It would be best to maintain backwards compatibility for a while and add a deprecation notice to the documentation. Sometime down the road we can then remove support for the old gem.
or cancel

Parsed with GitHub Flavored Markdown
4.

1 vote

God segfaults on new RE with thread patches
1 comment Created about 1 month ago by miv

Title

Body
Like this ----------------- Register state dump ---------------------- rax = 0x00000000011c959c rbx = 0x0000000001b81bd0 rcx = 0x0000000000000000 rdx = 0x0000000000e56c00 rdi = 0x0000000001b81bd0 rsi = 0x0000000000dc0600 rbp = 0x0000000000000001 rsp = 0x00000000299158b0 r8 = 0x0000000000000001 r9 = 0x0000000000000000 r10 = 0x0000000000000001 r11 = 0x0000000000000000 r12 = 0x0000000000000030 r13 = 0x0000000000000001 r14 = 0x00000000011b9508 r15 = 0x0000000000000000 rip = 0x00000000004138f7 rflags = 0x0000000000010202 cs = 0x0000000000000033 fs = 0x0000000001b81bd0 gs = 0x0000000024fc3f60 /opt/ruby-enterprise-1.8.7-20090928/lib/ruby/1.8/timeout.rb:92: [BUG] Segmentation fault ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 20090928 I tried SystemTimer instead of timeout and it seems to be working fine
or cancel
Like this

----------------- Register state dump ---------------------- rax = 0x00000000011c959c rbx = 0x0000000001b81bd0 rcx =
0x0000000000000000 rdx = 0x0000000000e56c00
rdi = 0x0000000001b81bd0 rsi = 0x0000000000dc0600 rbp =
0x0000000000000001 rsp = 0x00000000299158b0
r8 = 0x0000000000000001 r9 = 0x0000000000000000 r10 =
0x0000000000000001 r11 = 0x0000000000000000
r12 = 0x0000000000000030 r13 = 0x0000000000000001 r14 =
0x00000000011b9508 r15 = 0x0000000000000000
rip = 0x00000000004138f7 rflags = 0x0000000000010202 cs =
0x0000000000000033 fs = 0x0000000001b81bd0
gs = 0x0000000024fc3f60
/opt/ruby-enterprise-1.8.7-20090928/lib/ruby/1.8/timeout.rb:92: [BUG] Segmentation fault
ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux], MBARI 0x6770,
Ruby Enterprise Edition 20090928

I tried SystemTimer instead of timeout and it seems to be working fine

Comments
shadowhand Thu Oct 15 00:13:09 -0700 2009 | link
Same here with REE:

/opt/ruby-enterprise/lib/ruby/1.8/timeout.rb:92: [BUG] Segmentation fault ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 20090928
Comment
Same here with REE: <pre>/opt/ruby-enterprise/lib/ruby/1.8/timeout.rb:92: [BUG] Segmentation fault ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 20090928 </pre>
or cancel
Parsed with GitHub Flavored Markdown
5.

0 votes

"god check" failure
0 comments Created 29 days ago by shadowhand

Title

Body
Running "god check" results in: <pre><code> using event system: netlink starting event handler forking off new process forked process with pid = 3550 killing process [fail] never received process exit event </code></pre> The god log also says that events are not supported. However, "lsmod |grep cn" shows that it is loaded. It seems to me that god is incorrectly thinking that events are not supported on my system, or the documentation is incorrect. Using Arch Linux, kernel 2.6.24-xen on Slicehost.
or cancel
Running "god check" results in:
```
using event system: netlink
starting event handler
forking off new process
forked process with pid = 3550
killing process
[fail] never received process exit event
```
The god log also says that events are not supported. However, "lsmod |grep cn" shows that it is loaded. It seems to me that god is incorrectly thinking that events are not supported on my system, or the documentation is incorrect.

Using Arch Linux, kernel 2.6.24-xen on Slicehost.
Comments

Parsed with GitHub Flavored Markdown

Labels

The server is not available (or you do not have permissions to access it)

Comments

Twitter gem has changed

Comments

God segfaults on new RE with thread patches

Comments

"god check" failure

Comments