Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Info request error: Ошибка -1: Component unavailable #275

Closed
opiums9 opened this issue Feb 25, 2018 · 15 comments
Closed

Info request error: Ошибка -1: Component unavailable #275

opiums9 opened this issue Feb 25, 2018 · 15 comments

Comments

@opiums9
Copy link

opiums9 commented Feb 25, 2018

Hello, I decided to reinstall my Spectrum2 from version 2.0.3 to version 2.0.6. After reinstalling and running all the transports, I get an error in my jabber client: Info request error: Error -1: Component unavailable. As a jabber server, Prosody is used. In the server log, I was unable to detect errors. When executing the command in the spectrum2_manager status console, I get the answer Running, how can I solve this problem?
OS: Raspbian GNU / Linux 8.0 (jessie)
Sorry for my english (google translate).

@vitalyster
Copy link
Collaborator

You should have component info External component successfully authenticated entry in prosody.log

@opiums9
Copy link
Author

opiums9 commented Feb 25, 2018

But I get in the log: ...component warn Component not connected...
The configuration of transports coincides with the settings in prosody.

@vitalyster
Copy link
Collaborator

That is when server received a message to disconnected component, you should find why it is not connecting

@opiums9
Copy link
Author

opiums9 commented Feb 25, 2018

I do not see anything in the log, except:
Feb 25 22:12:02 icq.opiums.eu:component warn Component not connected, bouncing error for: <presence to='icq.opiums.eu' from='nickname@opiums.eu/QIP'>

@vitalyster
Copy link
Collaborator

Then you need to check spectrum log

@opiums9
Copy link
Author

opiums9 commented Feb 25, 2018

2018-02-25 21:20:30,895 INFO  XMPPFrontend: Creating component in gateway mode
2018-02-25 21:20:30,898 INFO  SQLite3Backend: Opening database /var/lib/spectrum2/icq.opiums.eu/database.sql
2018-02-25 21:20:30,908 INFO  NetworkPluginServer: Listening on host 127.0.0.1 port 34386
2018-02-25 21:20:30,908 INFO  NetworkPluginServer: Starting new backend /usr/bin/spectrum2_libpurple_backend --host 127.0.0.1 --port 34386 --service.backend_id=1 "-j" "icq.opiums.eu" "/etc/spectrum2/transports/icq.cfg" 
2018-02-25 21:20:30,911 INFO  NetworkPluginServer: Tried to spawn first backend with pid 5911
2018-02-25 21:20:30,911 INFO  NetworkPluginServer: Backend should now connect to Spectrum2 instance. Spectrum2 won't accept any connection before backend connects
2018-02-25 21:20:50,907 INFO  NetworkPluginServer: Sending PING to backends
2018-02-25 21:21:10,908 INFO  NetworkPluginServer: Sending PING to backends

@vitalyster
Copy link
Collaborator

How did you get spectrum for raspbian? Did you build packages yourself? It may be old issue with libmysqlclient 5.5 - #150

@opiums9
Copy link
Author

opiums9 commented Feb 25, 2018

I used the instruction Installing on other Debian/Ubuntu-based distributions

@vitalyster
Copy link
Collaborator

vitalyster commented Feb 25, 2018

As you are using jessie, I bet that you have libmysqlclient 5.5, please a) upgrade to stretch (and don't forget upgrade libmysqlclient-dev to libmariadbclient-dev) b) manually patch libpurple.h as mentioned in #150

@thundergreen
Copy link
Contributor

If u want armhf packages I have newest ;)

@opiums9
Copy link
Author

opiums9 commented Feb 26, 2018

Yes, where can I get them?

@thundergreen
Copy link
Contributor

I can upload them to my server and share them with u

@opiums9
Copy link
Author

opiums9 commented Feb 26, 2018

Well, I agree, thanks :)

@thundergreen
Copy link
Contributor

Can u wait till tonight? I'm at work actually

@opiums9
Copy link
Author

opiums9 commented Feb 26, 2018

Yes, of course

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants