Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: ReadyNAS remote binary crashing
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
03:31 AM
2012-10-09
03:31 AM
ReadyNAS remote binary crashing
Hi
I'm encountering problems with ReadyNAS remote 1.0.9.78 running on RAIDiator 4.2.22
leafp2p is crashing and I can not connect to my NAS via ReadyNAS Remote client on Windows 7 :
I'm encountering problems with ReadyNAS remote 1.0.9.78 running on RAIDiator 4.2.22
leafp2p is crashing and I can not connect to my NAS via ReadyNAS Remote client on Windows 7 :
./leafp2p -n
P2P Created by Pramod Immaneni and Jeff Capone
P2P Designed and Developed by Pramod Immaneni
Parsing config
service remote ReadyNAS Remote 0 1 0
*** glibc detected *** ./leafp2p: double free or corruption (out): 0x08207d78 ***
======= Backtrace: =========
/lib/libc.so.6[0xf7372935]
/lib/libc.so.6(cfree+0x9c)[0xf73747dc]
./leafp2p[0x80500f0]
./leafp2p[0x804cb96]
./leafp2p[0x804d0be]
./leafp2p[0x804d182]
/lib/libc.so.6(__libc_start_main+0xe5)[0xf731e455]
./leafp2p[0x804c641]
======= Memory map: ========
08048000-081f3000 r-xp 00000000 09:00 43132 /opt/p2p/bin/leafp2p
081f3000-081f4000 r--p 001aa000 09:00 43132 /opt/p2p/bin/leafp2p
081f4000-081f6000 rw-p 001ab000 09:00 43132 /opt/p2p/bin/leafp2p
081f6000-08242000 rw-p 00000000 00:00 0 [heap]
f7100000-f7121000 rw-p 00000000 00:00 0
f7121000-f7200000 ---p 00000000 00:00 0
f72c2000-f72d1000 r-xp 00000000 09:00 45490 /lib/libresolv-2.7.so
f72d1000-f72d3000 rw-p 0000e000 09:00 45490 /lib/libresolv-2.7.so
f72d3000-f72d5000 rw-p 00000000 00:00 0
f72d5000-f72d9000 r-xp 00000000 09:00 45484 /lib/libnss_dns-2.7.so
f72d9000-f72db000 rw-p 00003000 09:00 45484 /lib/libnss_dns-2.7.so
f72db000-f72dd000 r-xp 00000000 09:00 45076 /lib/libnss_mdns4_minimal.so.2
f72dd000-f72de000 rw-p 00001000 09:00 45076 /lib/libnss_mdns4_minimal.so.2
f72de000-f72e7000 r-xp 00000000 09:00 45485 /lib/libnss_files-2.7.so
f72e7000-f72e9000 rw-p 00008000 09:00 45485 /lib/libnss_files-2.7.so
f72ed000-f72ee000 rw-p 00000000 00:00 0
f72ee000-f72f0000 r-xp 00000000 09:00 45480 /lib/libdl-2.7.so
f72f0000-f72f2000 rw-p 00001000 09:00 45480 /lib/libdl-2.7.so
f72f2000-f72f3000 rw-p 00000000 00:00 0
f72f3000-f7307000 r-xp 00000000 09:00 240 /usr/lib/libz.so.1.2.3.3
f7307000-f7308000 rw-p 00013000 09:00 240 /usr/lib/libz.so.1.2.3.3
f7308000-f7440000 r-xp 00000000 09:00 45477 /lib/libc-2.7.so
f7440000-f7441000 r--p 00138000 09:00 45477 /lib/libc-2.7.so
f7441000-f7443000 rw-p 00139000 09:00 45477 /lib/libc-2.7.so
f7443000-f7446000 rw-p 00000000 00:00 0
f7446000-f7452000 r-xp 00000000 09:00 45213 /lib/libgcc_s.so.1
f7452000-f7453000 rw-p 0000b000 09:00 45213 /lib/libgcc_s.so.1
f7453000-f7477000 r-xp 00000000 09:00 45481 /lib/libm-2.7.so
f7477000-f7479000 rw-p 00023000 09:00 45481 /lib/libm-2.7.so
f7479000-f755c000 r-xp 00000000 09:00 901 /usr/lib/libstdc++.so.6.0.10
f755c000-f755f000 r--p 000e2000 09:00 901 /usr/lib/libstdc++.so.6.0.10
f755f000-f7561000 rw-p 000e5000 09:00 901 /usr/lib/libstdc++.so.6.0.10
f7561000-f7567000 rw-p 00000000 00:00 0
f7567000-f757b000 r-xp 00000000 09:00 45489 /lib/libpthread-2.7.so
f757b000-f757d000 rw-p 00013000 09:00 45489 /lib/libpthread-2.7.so
f757d000-f7580000 rw-p 00000000 00:00 0
f7580000-f76bd000 r-xp 00000000 09:00 4331 /usr/lib/i686/cmov/libcrypto.so.0.9.8
f76bd000-f76d5000 rw-p 0013c000 09:00 4331 /usr/lib/i686/cmov/libcrypto.so.0.9.8
f76d5000-f76d8000 rw-p 00000000 00:00 0
f76d8000-f771e000 r-xp 00000000 09:00 4332 /usr/lib/i686/cmov/libssl.so.0.9.8
f771e000-f7722000 rw-p 00046000 09:00 4332 /usr/lib/i686/cmov/libssl.so.0.9.8
f7725000-f7728000 rw-p 00000000 00:00 0
f7728000-f7742000 r-xp 00000000 09:00 45186 /lib/ld-2.7.so
f7742000-f7744000 rw-p 0001a000 09:00 45186 /lib/ld-2.7.so
ffb86000-ffba7000 rw-p 00000000 00:00 0 [stack]
ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso]
Aborted
Message 1 of 14
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
03:39 AM
2012-10-09
03:39 AM
Re: ReadyNAS remote binary crashing
What version of the p2p adapter is on your NAS?
Even if you don't intend to use it can you install the Replicate add-on via Add-Ons > Available. Not sure but that add-on might include an update to the p2p adapter.
Edit: That's probably not it, I guess. 4.2.22 was released the same day as the latest Replicate add-on.
Do you have Replicate installed? If so, what version?
Even if you don't intend to use it can you install the Replicate add-on via Add-Ons > Available. Not sure but that add-on might include an update to the p2p adapter.
Edit: That's probably not it, I guess. 4.2.22 was released the same day as the latest Replicate add-on.
Do you have Replicate installed? If so, what version?
Message 2 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
03:55 AM
2012-10-09
03:55 AM
Re: ReadyNAS remote binary crashing
Had it installed but removed now.
Tried to install the latest Replicate 1.1.5 - no difference - leafp2p is crashing while "registering node" process is ongoing client side.
Tried to install the latest Replicate 1.1.5 - no difference - leafp2p is crashing while "registering node" process is ongoing client side.
Message 3 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
04:03 AM
2012-10-09
04:03 AM
Re: ReadyNAS remote binary crashing
What does /var/log/frontview/initrd.log look like?
Message 4 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
04:09 AM
2012-10-09
04:09 AM
Re: ReadyNAS remote binary crashing
[2011/12/21 03:37:02] Factory default initiated due to new disks (no RAID, no partitions)!
[2011/12/21 03:47:39] Selected Flex-RAID mode, 20GB snapshot, RAID level 5
[2011/12/21 03:49:31] Factory default initiated on RAIDiator 4.2.19.
[2011/12/22 00:26:56] Updated from RAIDiator 4.2.19 to 4.2.19.
[2012/05/11 09:32:28] Updated from RAIDiator 4.2.19 to 4.2.20.
[2012/06/28 20:01:57] Updated from RAIDiator 4.2.20 to 4.2.21.
[2012/09/21 12:14:38] Updated from RAIDiator 4.2.21 to 4.2.22.
Message 5 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
04:11 AM
2012-10-09
04:11 AM
Re: ReadyNAS remote binary crashing
Interesting. That indicates you should not have issues from having a problematic update from having a very old version of Remote installed in the past.
But just to be sure can you post the output of the following?:
But just to be sure can you post the output of the following?:
# ls /opt
# ls -laR /opt/leaf /opt/p2p /opt/remote
Message 6 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
04:20 AM
2012-10-09
04:20 AM
Re: ReadyNAS remote binary crashing
ls /opt
p2p remote replication
ls -laR /opt/leaf /opt/p2p /opt/remote :
http://pastebin.com/HKmPnhTG
p2p remote replication
ls -laR /opt/leaf /opt/p2p /opt/remote :
http://pastebin.com/HKmPnhTG
Message 7 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
04:28 AM
2012-10-09
04:28 AM
Re: ReadyNAS remote binary crashing
What is strange discovered - when leafp2p is starting it's showing :
url https://peernetwork.netgear.com:443//peernetwork/services/LeafNetsConfigWebService
Setting parameter peer_host peerbroker.netgear.com
Setting parameter peer_port 443
Setting parameter event_host peerevent.netgear.com
Setting parameter event_port 443
but the host peerbroker.netgear.com 443 is NOT accessible :
telnet peerbroker.netgear.com 443
Trying 206.16.42.237...
telnet: connect to address 206.16.42.237: Connection timed out
while other two are accessible well ...
url https://peernetwork.netgear.com:443//peernetwork/services/LeafNetsConfigWebService
Setting parameter peer_host peerbroker.netgear.com
Setting parameter peer_port 443
Setting parameter event_host peerevent.netgear.com
Setting parameter event_port 443
but the host peerbroker.netgear.com 443 is NOT accessible :
telnet peerbroker.netgear.com 443
Trying 206.16.42.237...
telnet: connect to address 206.16.42.237: Connection timed out
while other two are accessible well ...
Message 8 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
04:39 AM
2012-10-09
04:39 AM
Re: ReadyNAS remote binary crashing
Typing that URL into my web browser I get a response.
Does rebooting your NAS make a difference?
Also for starting the leaf service use /etc/init.d/leafp2p
Does rebooting your NAS make a difference?
Also for starting the leaf service use /etc/init.d/leafp2p
Message 9 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
04:45 AM
2012-10-09
04:45 AM
Re: ReadyNAS remote binary crashing
I'm having no response in my browser as well for https://peerbroker.netgear.com ...
there you have traceroute :
2 115.70.192.9 2.221 ms 2.350 ms 2.498 ms
3 58.96.1.161 2.674 ms 3.282 ms 3.266 ms
4 * * *
5 203.131.62.156 54.127 ms 58.434 ms 54.157 ms
6 202.10.12.31 54.188 ms 53.455 ms 53.580 ms
7 202.10.10.86 58.477 ms 58.543 ms 58.539 ms
8 202.10.10.74 54.260 ms 53.803 ms 53.867 ms
9 202.10.12.8 57.804 ms 58.320 ms 58.422 ms
10 202.10.14.9 58.110 ms 58.026 ms 57.924 ms
11 202.50.238.213 58.199 ms 58.706 ms 58.630 ms
12 * * *
13 * * *
14 * * *
15 4.59.4.93 202.657 ms 202.716 ms 203.214 ms
16 4.69.152.143 236.706 ms 236.050 ms 235.648 ms
17 192.205.32.209 212.405 ms 210.786 ms 210.675 ms
18 12.122.114.6 230.141 ms 229.088 ms 229.683 ms
19 12.122.3.122 233.274 ms 233.413 ms 233.410 ms
20 12.122.31.190 230.939 ms 227.377 ms 230.403 ms
21 12.123.206.245 225.763 ms 223.558 ms 224.682 ms
22 12.122.254.50 226.673 ms 226.179 ms 225.483 ms
23 63.241.130.210 229.261 ms 228.709 ms 229.045 ms
24 63.241.152.108 230.118 ms 229.310 ms 230.444 ms
25 206.16.42.237 229.590 ms 229.211 ms 228.863 ms
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Rebooting NAS makes no difference - ReadyNAS remote is not working ...
for the last - yes /etc/init.d/leafp2p ...
there you have traceroute :
2 115.70.192.9 2.221 ms 2.350 ms 2.498 ms
3 58.96.1.161 2.674 ms 3.282 ms 3.266 ms
4 * * *
5 203.131.62.156 54.127 ms 58.434 ms 54.157 ms
6 202.10.12.31 54.188 ms 53.455 ms 53.580 ms
7 202.10.10.86 58.477 ms 58.543 ms 58.539 ms
8 202.10.10.74 54.260 ms 53.803 ms 53.867 ms
9 202.10.12.8 57.804 ms 58.320 ms 58.422 ms
10 202.10.14.9 58.110 ms 58.026 ms 57.924 ms
11 202.50.238.213 58.199 ms 58.706 ms 58.630 ms
12 * * *
13 * * *
14 * * *
15 4.59.4.93 202.657 ms 202.716 ms 203.214 ms
16 4.69.152.143 236.706 ms 236.050 ms 235.648 ms
17 192.205.32.209 212.405 ms 210.786 ms 210.675 ms
18 12.122.114.6 230.141 ms 229.088 ms 229.683 ms
19 12.122.3.122 233.274 ms 233.413 ms 233.410 ms
20 12.122.31.190 230.939 ms 227.377 ms 230.403 ms
21 12.123.206.245 225.763 ms 223.558 ms 224.682 ms
22 12.122.254.50 226.673 ms 226.179 ms 225.483 ms
23 63.241.130.210 229.261 ms 228.709 ms 229.045 ms
24 63.241.152.108 230.118 ms 229.310 ms 230.444 ms
25 206.16.42.237 229.590 ms 229.211 ms 228.863 ms
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Rebooting NAS makes no difference - ReadyNAS remote is not working ...
for the last - yes /etc/init.d/leafp2p ...
Message 10 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
05:17 AM
2012-10-09
05:17 AM
Re: ReadyNAS remote binary crashing
Try using the form here: http://www.readynas.com/forum/viewtopic.php?f=138&t=51197
Message 11 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
05:21 AM
2012-10-09
05:21 AM
Re: ReadyNAS remote binary crashing
A bit more :
I see in logs "Could not connect to server" ... that is probably due to not accessible IP from Australia ....
Interesting but that IP is not available from Europe as well :
telnet 206.16.42.237 443
Trying 206.16.42.237...
telnet: connect to address 206.16.42.237: Connection timed out
telnet: Unable to connect to remote host: Connection timed out
Who knows how to contact NetGear ????
Any suggestion ?
I see in logs "Could not connect to server" ... that is probably due to not accessible IP from Australia ....
Interesting but that IP is not available from Europe as well :
telnet 206.16.42.237 443
Trying 206.16.42.237...
telnet: connect to address 206.16.42.237: Connection timed out
telnet: Unable to connect to remote host: Connection timed out
Who knows how to contact NetGear ????
Any suggestion ?
Message 12 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
05:23 AM
2012-10-09
05:23 AM
Re: ReadyNAS remote binary crashing
Already done 🙂 Will see ...
Message 13 of 14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-09
05:26 AM
2012-10-09
05:26 AM
Re: ReadyNAS remote binary crashing
The form linked to in the post I linked to above is the best way to get in contact with the Remote team. Hopefully they can help resolve the issue for you.
Message 14 of 14