| View previous topic :: View next topic |
| Author |
Message |
TigerDragon
Voice
Joined: 19 Apr 2011
Posts: 2
|
 Posted: Tue Apr 19, 2011 8:14 pm Post subject: [solved] 1.8 snapshot and SSL |
 |
|
I have compiled eggdrop 1.8 snapshot on an openbsd alphaserver. When I attempt to run this version, it loads, but never connects to the server. I never see any connection attempt at the server side even. I get a large string of EAGAIN errors followed by a time out before it tries again.
The 1.6.18 with rootie ssl works fine from the same box, so outbound is not being blocked by firewall. I would really like to get this working. Can anyone assist?
Here is the SSL portion of the start up logs when running "eggdrop -n"
| Code: | [18:56:09] TLS: unable to load own certificate: error:02001002:system library:fopen:No such file or directory
[18:56:09] TLS: unable to load private key: error:20074002:BIO routines:FILE_CTRL:system lib
[18:56:09] main: entering loop
[18:56:09] Trying server [10.40.3.149]:+7000
[18:56:09] TLS: attempting SSL negotiation...
[18:56:09] TLS: state change: before/connect initialization
[18:56:09] TLS: state change: before/connect initialization
[18:56:09] TLS: state change: SSLv2/v3 write client hello B
[18:56:09] TLS: handshake in progress
[18:56:09] TLS: state change: SSLv2/v3 write client hello B
[18:56:10] TLS: state change: SSLv2/v3 write client hello B
[18:56:10] sockread EAGAIN: 10 35 (Resource temporarily unavailable)
[18:56:11] TLS: state change: SSLv2/v3 write client hello B
[18:56:11] sockread EAGAIN: 10 35 (Resource temporarily unavailable)
....
[18:57:18] Timeout: connect to 10.40.3.149
|
|
|
| Back to top |
|
 |
TigerDragon
Voice
Joined: 19 Apr 2011
Posts: 2
|
| Posted: Tue Apr 19, 2011 8:53 pm Post subject: |
|
|
And for other peoples' reference, to answer my own question:
I commented out the "vhost4" entry that was set and it works fine now. The box the eggdrop is running from has 2 ip addresses and the "dynamic" one is the default route. In the older version I had to use a "my-hostname" and that got carried over to a "vhost4" in the new config, but isn't needed. Removing the "set vhost4" allowed it to connect, so all is well now.
Sorry for cluttering the forum with my stupidity  |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
