lennartkoopmann / scopeport-web-interface
- Source
- Commits
- Network (1)
- Issues (11)
- Graphs
-
Branch:
master
-
DEPRECATION WARNING: months is deprecated and will be removed from Rails 2.3 (Fractional months are not respected. Convert value to integer before calling #months.). (called from send at /home/Ernesto/workspace/scopeport-web-interface/app/helpers/alarms_helper.rb:116)
Comments
-
Make services and service groups sortable
0 comments Created 6 months ago by lennartkoopmannIdea by Sven
Comments
-
Set correct permissions for conversationmessages and nodes
0 comments Created 5 months ago by lennartkoopmannAdministrator only
Comments
-
Notification receivers list: Only show enabled notification methods
0 comments Created 5 months ago by lennartkoopmannTitle
Comments
-
Suggested by a tester of the demo system.
Comments
-
Declaring emergencies as non-admin throws error message
0 comments Created 4 months ago by lennartkoopmannThis should be allowed for everyone
Comments
-
XMPP/Jabber alert messages not getting send?
7 comments Created 21 days ago by renemadsenIs it true that the XMPP/Jabber settings don't get used in the current state of the web interface?
Comments
lennartkoopmann
Tue Dec 08 07:47:04 -0800 2009
| link
The XMPP/Jabber settings are used. I am getting XMPP notifications via the configuration in the settings.
renemadsen
Tue Dec 08 08:27:38 -0800 2009
| link
After a new pull for 5 minutes ago I can't see that there has been send a XMMP/Jabber message. Should I be able to see it on the conversationmessages page?
I have enabled logging for XMMP/Jabber...
lennartkoopmann
Tue Dec 08 08:30:52 -0800 2009
| link
Yes you should be able to see the logged conversation in the conversationmessages page. There a a few factors that could block sending a message:
- Did you "attend" all alarms for this host? A new alarm is only generated (and though a new message is sent) every six hours for a sensor of a specific host. This time interval is not user definable yet.
- Did you enable XMPP at all?
- Did you define a notification group for the host that has a XMPP receiver?
renemadsen
Tue Dec 08 09:00:24 -0800 2009
| link
- Did you "attend" all alarms for this host? A new alarm is only generated (and though a new message is sent) every six hours for a sensor of a specific host. This time interval is not user definable yet. -- For the XMPP issue, it's right now for the service alarms. But, if I truncate the alarms table I might change the result?
- Did you enable XMPP at all? -- Checked and checked again, both in the interface and script/console
- Did you define a notification group for the host that has a XMPP receiver? -- Yes, and also checked both places.
lennartkoopmann
Tue Dec 08 14:42:20 -0800 2009
| link
No truncating the alarms table will not cause new service alarms to be sent. You'll also have to set the column "lastwarn" in the services table to NULL or 0. This is done automatically if you attend an alarm.
If this does not work: Could you provide me access to your web interface so I can check the issue?
lennartkoopmann
Wed Dec 09 05:17:04 -0800 2009
| link
Ah, your are using gmail.com as XMPP server. I guess this is for Google Talk? I never tried ScopePort XMPP with GTalk. Maybe there is a SSL/TLS issue? I'll try that out with my own Google account and keep you up to date!
renemadsen
Thu Dec 10 07:12:02 -0800 2009
| link
Yep, it's correct.
-
When using google mail as the smtp server for outboud alert mails it will fail with that message.
I'll try to solve this issue. It might be related to http://github.com/rails/rails/commit/732c724df61bc8b780dc42817625b25a321908e4 If so I'll post a patch for the web-interface code.
Comments
lennartkoopmann
Tue Dec 08 07:48:18 -0800 2009
| link
Yes, this might be reason. It would be great if you could supply a patch for this issue!
-
No route matches "/stylesheets/" with {:method=>:get}
0 comments Created 12 days ago by pocmoSometimes I get this error o_O
Processing ApplicationController#index (for 127.0.0.1 at 2009-12-17 19:27:52) [GET]
ActionController::RoutingError (No route matches "/stylesheets/" with {:method=>:get}):
/usr/lib/ruby/1.8/webrick/httpserver.rb:104:inservice' /usr/lib/ruby/1.8/webrick/httpserver.rb:65:inrun' /usr/lib/ruby/1.8/webrick/server.rb:173:instart_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:instart' /usr/lib/ruby/1.8/webrick/server.rb:162:instart_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:instart' /usr/lib/ruby/1.8/webrick/server.rb:92:ineach' /usr/lib/ruby/1.8/webrick/server.rb:92:instart' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start'Comments
-
Attending a "host offline" alarm must reset the warning time
0 comments Created about 13 hours ago by lennartkoopmannAIT
Comments





What is that send() function? I took a look at it but not yet sure how to solve it. Did you investigate this issue yet?