I have no log folder under /mnt/STORAGE/jails/crashplan_1/usr/pbi/crashplan-amd64/share/crashplan/Ī mmoment ago, I tried removing the jail completely, rebooting, reinstalling, rebooting, and still the same effect. I just installed the plugin: I don't get it to launch even once. It's a fresh install: I'm starting to use crashplan on freenas for backup purposes. This appears in the log when starting, idk if it might shed some light on the problem Jan 26 16:58:47 NAS manage.py: Couldn't retrieve : timed out Jan 26 16:58:37 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b Jan 26 16:58:37 NAS kernel: epair0a: promiscuous mode enabled Jan 26 16:58:37 NAS kernel: epair0b: link state changed to UP Jan 26 16:58:37 NAS kernel: epair0a: link state changed to UP Jan 26 16:58:37 NAS kernel: lagg0: promiscuous mode enabled Jan 26 16:58:37 NAS kernel: bce0: promiscuous mode enabled Jan 26 16:58:37 NAS kernel: bridge0: link state changed to UP Jan 26 16:58:37 NAS kernel: bce1: promiscuous mode enabled
Jan 26 16:58:21 NAS smbd: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
lib/util/become_daemon.c:136(daemon_ready) Jan 26 16:58:20 NAS winbindd: initialize_winbindd_cache: clearing cache and re-creating with version number 2 source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache) Jan 26 16:58:20 NAS generate_smb4_conf.py: Popen()ing: /usr/local/bin/net sam rights grant root SeTakeOwnershipPrivilege SeBackupPrivilege SeRestorePrivilege Jan 26 16:58:20 NAS generate_smb4_conf.py: Popen()ing: /usr/local/bin/pdbedit -L Jan 26 16:58:18 NAS generate_smb4_conf.py: Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpW6FjSw -s /usr/local/etc/nf -e tdbsam:/var/etc/private/passdb.tdb Jan 26 16:58:18 NAS generate_smb4_conf.py: Popen()ing: zfs list -H -o mountpoint Jan 26 16:58:18 NAS generate_smb4_conf.py: Popen()ing: zfs list -H -o mountpoint,name Jan 26 16:58:18 NAS generate_smb4_conf.py: Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Jan 26 16:58:11 NAS WARNING: 192.168.1.4 (:): no ping reply (NOP-Out) after 5 seconds dropping connection Jan 26 16:58:06 NAS vboxdrv: fAsync=0 offMin=0x41a offMax=0xdad2 Jan 26 16:58:06 NAS root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Jan 26 16:58:04 NAS ctld: auth-group "ag4tg_1" not assigned to any target Jan 26 16:58:04 NAS ctld: invalid target name "nasr:crashplan" should start with either ".iqn", "eui.", or "naa." Jan 26 16:58:03 NAS kernel: bce0: link state changed to UP Just restarting the jail doesn't always work for some reason.Ĭode: Jan 26 16:58:03 NAS kernel: bce0: link state changed to UP GUI_JAVA_OPTS=".SelectorProvider=.PollSelectorProvider -Dfile.encoding=UTF-8 -Dapp=CrashPlanDesktop -DappBaseName=CrashPlan -Xms20m -Xmx512m 4Stack=true =300 =300 .ttl=0 =0 =false"Īlso, many of us had to reboot the entire FreeNAS for the plugin to correctly show that it is running. SRV_JAVA_OPTS=".SelectorProvider=.PollSelectorProvider -Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx1024m 4Stack=true =300 =300 .ttl=0 =0 =false" Here is my run.conf for comparison if it helps: Look for "CPVERSION" in this file to see which version is installed on your server: /usr/pbi/crashplan-amd64/share/crashplan/log/app.log. That would mean you have something else going on.
#Update crashplan update#
If run.conf already has the suggested first two entries and you did not recently did not add them, then you probably did not take the 3.7.0 update, because the update is what wipes them out. If not, you may just need to start over with the plugin. First, I'm assuming that this was working until a couple of weeks ago when the 3.7.0 update came out.
0 kommentar(er)
