Issues with FreeNAS after changing networking stuff to a new place in the house...

[rodofrn]

Hello guys, little bit of background...So, today in the morning everything was working flawlessly, all my jails were running, webgui working, etc. Then in the afternoon I changed everything to a new place in the house and reconnected all the cables. I have a Modem-->Router-->Switch+Freenas (switch and freenas connected to router.). NOTE: FreeNAS used to be connected to the switch before the changes, does it make a difference?
Now, after a lot of trial and error, I was able to connect to the WebGUI, but all my jails are DOWN. I get this error in the console thing in freenas...

May 1 17:34:51 freenas manage.py: [freeadmin.navtree:629] An error occurred while unserializing from http://192.168.0.104/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
May 1 17:34:51 freenas manage.py: [freeadmin.navtree:629] An error occurred while unserializing from http://192.168.0.104/plugins/transmission/5/_s/treemenu: No JSON object could be decoded

Here is the ping to my computer from the jails console...

root@sabnzbd_1:/ # ping 192.168.0.138
PING 192.168.0.138 (192.168.0.138): 56 data bytes
64 bytes from 192.168.0.138: icmp_seq=0 ttl=128 time=0.362 ms
64 bytes from 192.168.0.138: icmp_seq=1 ttl=128 time=0.341 ms
64 bytes from 192.168.0.138: icmp_seq=2 ttl=128 time=0.350 ms
64 bytes from 192.168.0.138: icmp_seq=3 ttl=128 time=0.353 ms
64 bytes from 192.168.0.138: icmp_seq=4 ttl=128 time=0.255 ms
64 bytes from 192.168.0.138: icmp_seq=5 ttl=128 time=0.283 ms
64 bytes from 192.168.0.138: icmp_seq=6 ttl=128 time=0.342 ms
64 bytes from 192.168.0.138: icmp_seq=7 ttl=128 time=0.136 ms
^C
--- 192.168.0.138 ping statistics ---
8 packets transmitted, 8 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.136/0.303/0.362/0.072 ms
root@sabnzbd_1:/ #

Does anybody know what is going on? Please help me..!

Thanks in advance.

 

[Joshua Parker Ruehlig]

The middleware part of the FreeNAS9 plugins system can be sensative/unreliable. Have you tried restarting the jail since getting networking working in the jail?

 

[rodofrn]

The middleware part of the FreeNAS9 plugins system can be sensative/unreliable. Have you tried restarting the jail since getting networking working in the jail?

I have restarted the jail, and nothing...this is the log console thingy...

May 1 18:01:23 freenas manage.py: [freeadmin.navtree:629] An error occurred while unserializing from http://192.168.0.104/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
May 1 18:01:23 freenas manage.py: [freeadmin.navtree:629] An error occurred while unserializing from http://192.168.0.104/plugins/transmission/5/_s/treemenu: No JSON object could be decoded
May 1 18:01:34 freenas manage.py: [freeadmin.navtree:629] An error occurred while unserializing from http://192.168.0.104/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
May 1 18:01:34 freenas manage.py: [freeadmin.navtree:629] An error occurred while unserializing from http://192.168.0.104/plugins/transmission/5/_s/treemenu: No JSON object could be decoded
May 1 18:02:12 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.0.104/plugins/transmission/5/_s/status: No JSON object could be decoded
May 1 18:02:12 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.0.104/plugins/plexmediaserver/1/_s/status: No JSON object could be decoded
May 1 18:02:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/tank/jails/.warden-template-VirtualBox-4.3.12'
May 1 18:02:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/tank/jails/ownCloud'
May 1 18:02:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/tank/jails/Murmur'
May 1 18:02:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/tank/jails/TeamSpeak3'
May 1 18:02:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/tank/jails/subsonic_1'
May 1 18:02:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/tank/jails/plexmediaserver_1'
May 1 18:02:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/tank/jails/PlexConnect'
May 1 18:02:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/tank/jails/sabnzbd_1'
May 1 18:03:04 freenas manage.py: [freeadmin.navtree:629] An error occurred while unserializing from http://192.168.0.104/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
May 1 18:03:04 freenas manage.py: [freeadmin.navtree:629] An error occurred while unserializing from http://192.168.0.104/plugins/transmission/5/_s/treemenu: No JSON object could be decoded

 

[Jacopx]

are the jail IP address free in your network?

 

[joeschmuck]

As for your router question, well that depends on how the router firmware is setup. You gave no details about the router, firmware it's running, etc... If it's a standard home router running a default type setup, all the LAN ports should be identical to if you just used a switch. You might have an exception where the router might have 100Mbps ports vice 1Gbps ports but that shouldn't cause the issue you are seeing. Try to put the system back the way it was and see if that fixes the problem. If it does then you have an issue with your router. I've got to admit that it's a bit far fetched though that it's the router but it could be causing issues with your IP addresses.

 

[depasseg]

NOTE: FreeNAS used to be connected to the switch before the changes, does it make a difference?

No, it won't matter, unless the switch was actually an old router handing out DHCP addresses.

What was the address of FreeNas and the jails before the move?
If you move the machine back, does it work properly?

 

[rodofrn]

As for your router question, well that depends on how the router firmware is setup. You gave no details about the router, firmware it's running, etc... If it's a standard home router running a default type setup, all the LAN ports should be identical to if you just used a switch. You might have an exception where the router might have 100Mbps ports vice 1Gbps ports but that shouldn't cause the issue you are seeing. Try to put the system back the way it was and see if that fixes the problem. If it does then you have an issue with your router. I've got to admit that it's a bit far fetched though that it's the router but it could be causing issues with your IP addresses.

The router is a standard home router linksys e5000 something like that...

No, it won't matter, unless the switch was actually an old router handing out DHCP addresses.

What was the address of FreeNas and the jails before the move?
If you move the machine back, does it work properly?

the IP's are ALL the same. I cant move it back :)

Joshua is saying that it could be a problem with permissions/users because i get the weird pam system error. ill try to setup a new jail and see if it works.

 

[Robert Trevellyan]

Did the router and/or modem get power cycled during the move? If so, I'm betting on an IP clash due to a change in DHCP assignments. Make sure any fixed IP addresses you have set up on your network do not fall within the DHCP address range delivered by whichever device is your DHCP server.

 

[nojohnny101]

i'm going to go with most here and point to IP clashes or DHCP reservations expiring.

Did you set up static IPs for your jails initially in the old location?

 

[rodofrn]

Well, I always set STATIC IP's for everything. I redid the whole thing, and now it is working PERFECTLY, no issues at all, although I am seeing a lot of these again...

Code:

May 14 09:38:54 freenas kernel: arp: 192.168.0.105 moved from 02:ff:20:00:0a:0a to 0c:c4:7a:c5:16:48 on epair5b
May 14 10:28:47 freenas kernel: arp: 192.168.0.105 moved from 02:ff:20:00:0a:0a to 0c:c4:7a:c5:16:48 on epair5b
May 14 13:23:42 freenas kernel: arp: 192.168.0.105 moved from 02:ff:20:00:0a:0a to 0c:c4:7a:c5:16:48 on epair5b
May 14 19:04:45 freenas kernel: arp: 192.168.0.105 moved from 02:ff:20:00:0a:0a to 0c:c4:7a:c5:16:48 on epair5b
May 14 20:19:26 freenas kernel: arp: 192.168.0.105 moved from 02:ff:20:00:08:0a to 0c:c4:7a:c5:16:48 on epair3b

Does ANYBODY know what it could be?

 

[nojohnny101]

Glad you got it working.

What version of FreeNAS are you running?

 

[rodofrn]

Glad you got it working.

What version of FreeNAS are you running?

thanks.

Code:

Build    FreeNAS-9.10-STABLE-201605021851 (35c85f7)
Platform    Intel(R) Core(TM) i3-4370 CPU @ 3.80GHz
Memory    16314MB
System Time    Sat May 14 20:55:50 PDT 2016
Uptime    8:55PM up 9 days, 6:20, 0 users
Load Average    2.39, 2.28, 1.97

 

[depasseg]

Well, I always set STATIC IP's for everything. I redid the whole thing, and now it is working PERFECTLY, no issues at all, although I am seeing a lot of these again...

Code:

May 14 09:38:54 freenas kernel: arp: 192.168.0.105 moved from 02:ff:20:00:0a:0a to 0c:c4:7a:c5:16:48 on epair5b
May 14 10:28:47 freenas kernel: arp: 192.168.0.105 moved from 02:ff:20:00:0a:0a to 0c:c4:7a:c5:16:48 on epair5b
May 14 13:23:42 freenas kernel: arp: 192.168.0.105 moved from 02:ff:20:00:0a:0a to 0c:c4:7a:c5:16:48 on epair5b
May 14 19:04:45 freenas kernel: arp: 192.168.0.105 moved from 02:ff:20:00:0a:0a to 0c:c4:7a:c5:16:48 on epair5b
May 14 20:19:26 freenas kernel: arp: 192.168.0.105 moved from 02:ff:20:00:08:0a to 0c:c4:7a:c5:16:48 on epair3b

Does ANYBODY know what it could be?

It means that 192.168.0.105 has changed source MAC's. This can be due to a device that moves from one access point to another, or a machine that has wired and wireless connections and is bouncing back and forth. Or it could be something completely different (aka, I don't know). I found a sysctl tunable around here to disable the reporting of it.