jadestorm

Lots of weird behavior as of Wildfire 3.0.0

Discussion created by jadestorm Champion on Jul 3, 2006
Latest reply on Sep 11, 2006 by AWenckus

Hi!

 

I don''t actively use Asterisk-IM right now, but I tend to keep a lot of the plugins installed just to look at them and such.  As of 3.0.0, the Asterisk-IM plugin does not seem to function at all.  I''ll go into the various -isms individually:

 

Using the new plugin manager, if I go to restart or delete this plugin, I get:

cut

HTTP ERROR: 500

 

Internal Server Error

 

RequestURI=/plugin-admin.jsp

 

Powered by Jetty://

/cut

 

If I go to auto-upgrade it (I had a 1.1 to 1.1.1 upgrade pending), it says Upgrade complete, but then nothing happens.

 

In my info logs, I get this over and over again:

2006.07.03 21:38:30 unloading asterisk-im plugin resources

2006.07.03 21:38:30 Unregistering asterisk-im plugin as a component

2006.07.03 21:38:51 unloading asterisk-im plugin resources

2006.07.03 21:38:51 Unregistering asterisk-im plugin as a component

2006.07.03 21:39:11 unloading asterisk-im plugin resources

2006.07.03 21:39:11 Unregistering asterisk-im plugin as a component

2006.07.03 21:39:31 unloading asterisk-im plugin resources

2006.07.03 21:39:31 Unregistering asterisk-im plugin as a component

2006.07.03 21:39:51 unloading asterisk-im plugin resources

2006.07.03 21:39:51 Unregistering asterisk-im plugin as a component

2006.07.03 21:41:14 unloading asterisk-im plugin resources

2006.07.03 21:41:14 Unregistering asterisk-im plugin as a component

 

Similar message in debug log.  Nothing else really useful in that regard.

 

No Asterisk tab like what used to exist.

 

I tried removing the plugin entirely and then using the web interface to install the latest version.  Same thing happens.

 

I''m going to remove the plugin for now so it stops bothering me logs, but hey.  =)  Any ideas?

Outcomes