Hi,
I upgraded FreeNAS from 9.3.1 to 9.10 STABLE without deleting my jails dataset. Now I can't start the crashplan service in my crashplan jail.
After a fresh reboot of FreeNAS the jail starts (and receives an IP) but the service does not start. Trying to start the service from the FreeNAS GUI returns "Some error occurred". Nothing is added to /var/log/messages.
When I go to the crashplan jail on the CLI and run "service crashplan onestart" I get:
I googled that error and found this bug report, but that doesn't seem to be my issue because the linux kernel module is loaded:
When I restart the jail from the FreeNAS GUI, the jail restarts but does not get an IP, and I have the following in /var/log/messages:
However I can enter the jail and run "dhclient epair0b", which successfully assigns the correct IP to the jail.
I'd appreciate any troubleshooting suggestions, because right now my backup isn't working, which is less than ideal...
Thanks for reading!
Tom
I upgraded FreeNAS from 9.3.1 to 9.10 STABLE without deleting my jails dataset. Now I can't start the crashplan service in my crashplan jail.
After a fresh reboot of FreeNAS the jail starts (and receives an IP) but the service does not start. Trying to start the service from the FreeNAS GUI returns "Some error occurred". Nothing is added to /var/log/messages.
When I go to the crashplan jail on the CLI and run "service crashplan onestart" I get:
Code:
/usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset Starting CrashPlan Engine ... Using standard startup OK
I googled that error and found this bug report, but that doesn't seem to be my issue because the linux kernel module is loaded:
Code:
$ kldload linux kldload: can't load linux: module already loaded or in kernel
When I restart the jail from the FreeNAS GUI, the jail restarts but does not get an IP, and I have the following in /var/log/messages:
Code:
Mar 30 22:43:28 freenas kernel: epair0a: link state changed to DOWN Mar 30 22:43:28 freenas kernel: epair0a: link state changed to DOWN Mar 30 22:43:28 freenas kernel: epair0b: link state changed to DOWN Mar 30 22:43:28 freenas kernel: epair0b: link state changed to DOWN Mar 30 22:43:32 freenas kernel: ifa_del_loopback_route: deletion failed: 48 Mar 30 22:43:32 freenas Freed UMA keg (udp_inpcb) was not empty (240 items). Lost 24 pages of memory. Mar 30 22:43:32 freenas Freed UMA keg (udpcb) was not empty (2171 items). Lost 13 pages of memory. Mar 30 22:43:32 freenas Freed UMA keg (tcp_inpcb) was not empty (90 items). Lost 9 pages of memory. Mar 30 22:43:32 freenas Freed UMA keg (tcpcb) was not empty (27 items). Lost 9 pages of memory. Mar 30 22:43:32 freenas Freed UMA keg (ripcb) was not empty (30 items). Lost 3 pages of memory. Mar 30 22:43:32 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required Mar 30 22:43:32 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required Mar 30 20:43:32 freenas devd: Executing '/etc/pccard_ether epair0a start' Mar 30 20:43:32 freenas devd: Executing '/etc/pccard_ether epair0b start' Mar 30 20:43:32 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair0a' Mar 30 22:43:32 freenas epair0a: Ethernet address: 02:ff:60:00:07:0a Mar 30 22:43:32 freenas epair0b: Ethernet address: 02:ff:b0:00:0a:0b Mar 30 22:43:32 freenas kernel: epair0a: link state changed to UP Mar 30 22:43:32 freenas kernel: epair0a: link state changed to UP Mar 30 22:43:32 freenas kernel: epair0b: link state changed to UP Mar 30 22:43:32 freenas kernel: epair0b: link state changed to UP Mar 30 22:43:32 freenas kernel: epair0a: promiscuous mode enabled Mar 30 22:43:32 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b Mar 30 22:43:32 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b Mar 30 22:43:43 freenas manage.py: [freeadmin.navtree:621] An error occurred while unserializing from http://192.168.1.206/plugins/crashplan/1/_s/treemenu: No JSON object could be decoded
However I can enter the jail and run "dhclient epair0b", which successfully assigns the correct IP to the jail.
Code:
DHCPREQUEST on epair0b to 255.255.255.255 port 67 DHCPACK from 192.168.1.100 bound to 192.168.1.208 -- renewal in 21600 seconds.
I'd appreciate any troubleshooting suggestions, because right now my backup isn't working, which is less than ideal...
Thanks for reading!
Tom