step 1 - restart your name server
watch to make sure it restarts properly
step 2 - restart your web server
watch to make sure it restarts properly.
step 3 try verify_install again.
this problem is local to your machine.
I have seen this problem happen with servers where the nameserver has
become flaky.
At 11:18 AM 12/21/2001 -0500, Alexey Zilber wrote:
>We've had our scripts running for months without any problems. Suddenly
>they all stop working. It's been 2 days now that the problem has been going
>on and our clients going ape shit! I've recieved no replies either from
>opensrs emergency support, nor the support email itself. What's up??
>
>Here's the output of verify_install.cgi, pls note again, these scripts have
>been running fine for months.
>
>Alex
>
>_________OpenSRS Client Debugger__________
>
>Operating System : Linux dayak.com 2.4.10-ac4 #3 Thu Oct 4
>15:04:03 EDT 2001 i686 unknown
>Perl compiled for : linux (i386-linux)
>Client Version : XML:2.2.2
>Server Hostname : rr-n1-tor.opensrs.net
>Server Port : 55000
>Reseller Username : koguma
>Private Key Length : 111
>Encryption method : Blowfish
>Checking for Digest::MD5 : OK (version 2.16)
>Checking for Crypt::DES : OK
>Checking for Crypt::Blowfish : OK (version 2.06)
>Checking for Crypt::CBC : OK (version 1.25)
>Checking for XML::Parser : OK (version 2.30)
>Checking for Unicode::Map : OK (version 0.110)
>Checking for Unicode::String : OK (version 2.06)
>Logging in to OpenSRS server : ERROR: Unable to establish socket!
