NeoRouter http://www.neorouter.com/forum/ |
|
nrserver failed to start error -2147024848 freebsd [SOLVED] http://www.neorouter.com/forum/viewtopic.php?f=8&t=4795 |
Page 1 of 2 |
Author: | zloben [ Sun Sep 25, 2011 3:45 am ] |
Post subject: | nrserver failed to start error -2147024848 freebsd [SOLVED] |
Hi all. Didn't find the answer through search, so I have to ask directly. FreeBSD 8.1 x32, fresh install. Client works fine (connected to test server on XP, ok). But there are problems with server. I created a domain, added a user but then... First, I couldn't connect to it even locally with error 0x80070039. I started digging and found, that the server didn't start. nrserver -run fails with "nrserver failed to start due to error -2147024848" nrserver -run --dbroot /usr/home/xxxx/neor failed with "nrserver failed to start due to error -2139029481" I don't even know, what does the error codes mean, so I'm stuck. Help me, please |
Author: | zloben [ Sun Sep 25, 2011 12:52 pm ] |
Post subject: | Re: nrserver failed to start due to error -2147024848 freebsd |
Just to be sure - here's process list... Running under root account. Looks like nrserver is up, but still cannot connect. What am I missing here? Any help would be appreciated... tbsd# ps -ax PID TT STAT TIME COMMAND 0 ?? DLs 0:00.63 [kernel] 1 ?? ILs 0:00.07 /sbin/init -- 2 ?? DL 0:01.48 [g_event] 3 ?? DL 0:00.29 [g_up] 4 ?? DL 0:00.80 [g_down] 5 ?? DL 0:00.00 [mpt_recovery0] 6 ?? DL 0:00.14 [fdc0] 7 ?? DL 0:00.00 [sctp_iterator] 8 ?? DL 0:00.00 [xpt_thrd] 9 ?? DL 0:00.04 [pagedaemon] 10 ?? DL 0:00.00 [audit] 11 ?? RL 604:19.76 [idle] 12 ?? WL 0:48.92 [intr] 13 ?? DL 0:01.34 [yarrow] 14 ?? DL 0:00.00 [vmdaemon] 15 ?? DL 0:00.00 [pagezero] 16 ?? DL 0:00.15 [bufdaemon] 17 ?? DL 0:00.13 [vnlru] 18 ?? DL 0:01.02 [syncer] 19 ?? DL 0:00.56 [softdepflush] 20 ?? DL 0:00.10 [flowcleaner] 493 ?? Ss 0:00.01 /sbin/devd 626 ?? Ss 0:00.40 /usr/sbin/syslogd -s 769 ?? Is 0:03.12 /usr/local/bin/nrservice 772 ?? Is 0:01.04 /usr/local/bin/nrserver 988 ?? Ss 0:00.01 /usr/sbin/sshd 996 ?? Ss 0:00.92 sendmail: accepting connections (sendmail) 1000 ?? Is 0:00.03 sendmail: Queue runner@00:30:00 for /var/spool/client 1007 ?? Is 0:00.77 /usr/sbin/cron -s 2157 ?? Ss 0:00.08 sshd: zloben [priv] (sshd) 2160 ?? S 0:00.01 sshd: zloben@pts/0 (sshd) 1304 v0 Is+ 0:00.01 /usr/libexec/getty Pc ttyv0 1081 v1 Is+ 0:00.01 /usr/libexec/getty Pc ttyv1 1082 v2 Is+ 0:00.00 /usr/libexec/getty Pc ttyv2 1083 v3 Is+ 0:00.00 /usr/libexec/getty Pc ttyv3 1084 v4 Is+ 0:00.00 /usr/libexec/getty Pc ttyv4 1085 v5 Is+ 0:00.00 /usr/libexec/getty Pc ttyv5 1086 v6 Is+ 0:00.00 /usr/libexec/getty Pc ttyv6 1087 v7 Is+ 0:00.00 /usr/libexec/getty Pc ttyv7 2161 0 Ss 0:00.01 -sh (sh) 2162 0 S 0:00.01 su 2163 0 R 0:00.01 _su (csh) 2167 0 R+ 0:00.00 ps -ax |
Author: | luke [ Sun Sep 25, 2011 7:47 pm ] |
Post subject: | Re: nrserver failed to start due to error -2147024848 freebsd |
hi zloben, Thank you for using NeoRouter. Errors starting with 0x8007???? are system errors, and you can look them up in errno.h. 0x80070039 is ENOTCONN. -2147024848 = 0x80070030, is EADDRINUSE. It means nrserver already started and is bound to port 32976. Code: from errno.h #define ENOTCONN 57 /* Socket is not connected */ #define EADDRINUSE 48 /* Address already in use */ Error 0x80810017 means nrserver cannot find the SSL certificate files, because you changed dbroot. Thanks, Luke |
Author: | zloben [ Mon Sep 26, 2011 4:47 am ] |
Post subject: | Re: nrserver failed to start due to error -2147024848 freebsd |
Thanks for the reply, Luke. I've changed dbroot back to /usr/local/ZebraNetworkSystems/Neorouter, so I'm stuck where I've started - fighting with the "Socket is not connected" error when connecting locally (i.e. to the server at the same machine). I'll try to connect from another machine later (with XP or Ubuntu) and see what error will it produce... But still - maybe you can point me, how can I get past this error? Even the direction will be appreciated, because google didn't help me. Please, help |
Author: | zloben [ Mon Sep 26, 2011 10:09 am ] |
Post subject: | Re: nrserver failed to start due to error -2147024848 freebsd |
XP fails to connect with error 0x 80072749 Ubuntu fails to connect with error 0x 8007006b Since it's happening even with a wrong username/password, I assume it's a problem with connection to neorouter server... Still stuck |
Author: | luke [ Mon Sep 26, 2011 9:43 pm ] |
Post subject: | Re: nrserver failed to start due to error -2147024848 freebsd |
hi zloben, The error is most likely caused by firewall or hairpin. Please follow the trouble shooting guide in User's Manual "section 7.1" (http://www.neorouter.com/Documents.html). Thanks, Luke |
Author: | zloben [ Mon Oct 10, 2011 5:39 am ] |
Post subject: | Re: nrserver failed to start due to error -2147024848 freebsd |
Hi Luke. I followed the troubleshooting guide, but, as I said, it's a fresh install of FreeBSD without anything enabled. But I checked it, just to be sure - it's not enabled Looks like the server is listening to IPv6, ignoring Features.ini Code: tbsd# netstat -a | grep LISTEN tcp4 0 0 localhost.smtp *.* LISTEN tcp4 0 0 *.ssh *.* LISTEN tcp6 0 0 *.ssh *.* LISTEN tcp4 0 0 localhost.32975 *.* LISTEN tcp6 0 0 *.nrserver *.* LISTEN Feature.ini consists only of Code: #Description: Specify host IP type for nrserver #Options: 0-detect; 1-IPv4; 2-IPv6; 3-Dual #Default: 0 HostIPType=0 I've read about some problem in Freebsd with 3-symbol network adapter, but mine is em0, not msk0 or something. Is there any way to make it follow the options in the Feature.ini file? Or shall I really try to pluck the ipv6 out of the FreeBSD core? |
Author: | luke [ Sat Oct 15, 2011 8:51 am ] |
Post subject: | Re: nrserver failed to start due to error -2147024848 freebsd |
hi zloben, Issue 1 - HostIPType setting: If the value is 0, NeoRouter will automatically detect whether your computer supports IPv6. If NeoRouter listens at IPv6, it will accept both v6 and v4 incoming connections. To force NeoRouter to listen at IPv4 only, you can set HostIPType to 1. Issue 2 - network adapter names You can use the following setting to override the default detection logic. In your case, you can put "NicInterfaceName=em". Code: #Description: Network Interface name used for getting MAC address #Options: the primary network interface having MAC address #Default: eth (on Linux) or ed (on FreeBSD) NicInterfaceName=eth Thanks, Luke |
Author: | zloben [ Mon Oct 17, 2011 5:03 am ] |
Post subject: | Re: nrserver failed to start due to error -2147024848 freebsd |
Sorry, I've copied the template, not the real file listing. Of course, it was 1, not 0 - that's why I wrote "it ignores Features.ini". I'll try the 2nd way you described, maybe it'll help. Thanks a lot! |
Author: | zloben [ Mon Oct 17, 2011 9:34 am ] |
Post subject: | Re: nrserver failed to start due to error -2147024848 freebsd |
Nope, stuck at the same point. Still listening to IPv6, still cannot connect due to "socket not connected", still suspecting the ignoring the feature.ini file. Well...... I'm sorry for being troublesome, but the same problem appears on EVERY FreeBSD system I make. I'll try to set up a 8.2 version of FreeBSD on a new virtual machine, but I doubt it will help. |
Page 1 of 2 | All times are UTC - 5 hours |
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |