nickt
Contributor
- Joined
- Feb 27, 2015
- Messages
- 131
So I'm pretty sure @Andrew076's method worked for me. I ran through without any real difficulties, and CrashPlan appears to be up and running again. The only thing that is a bit odd is that my process list and socket lists look a little short.
Rather different to @Andrew076's list and considerably shorter than I am used to in the past. Similarly:
I'm used to seeing a huge list of java processes in previous versions.
But it all seems to be working. I could rescan the backup list and crashplan is now dutifully sending files out to the cloud to be backed up. Bitrate, progress, time remaining all look right. The server version reported in the GUI is now saying 4.8, rather than 4.7, and there are no "upgrade failed" banners in the GUI.
So I don't know - doesn't look quite right to me - but seems to be working!
Nick
Code:
[root@crashplan_1 /]# sockstat -l sockstat: struct xtcpcb size mismatch USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root java 12870 89 stream (not connected) root java 12870 101 stream(not connected) root syslogd 11366 4 dgram /var/run/log root syslogd 11366 5 dgram /var/run/logpriv root syslogd 11366 6 udp4 10.0.0.153:514 *:*
Rather different to @Andrew076's list and considerably shorter than I am used to in the past. Similarly:
Code:
[root@crashplan_1 /]# ps aux USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 12870 70.7 2.9 2276360 485380 0 INJ 4:56PM 8:53.06 /usr/pbi/crashplan-amd64/jre-linux-i586-1.8.0_72/jre/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile. root 11366 0.0 0.0 12092 1564 ?? SsJ 4:53PM 0:00.01 /usr/sbin/syslogd -s root 11440 0.0 0.0 14188 1668 ?? SsJ 4:53PM 0:00.01 /usr/sbin/cron -s root 11685 0.0 0.2 154020 36372 ?? SJ 4:53PM 0:06.18 /usr/pbi/crashplan-amd64/bin/python2.7 /usr/pbi/crashplan-amd64/control.py start 10.0.0.153 12350 root 12285 0.0 0.0 17528 2952 0 SJ 4:53PM 0:00.03 bash root 14103 0.0 0.0 16300 1688 0 R+J 5:08PM 0:00.00 ps aux
I'm used to seeing a huge list of java processes in previous versions.
But it all seems to be working. I could rescan the backup list and crashplan is now dutifully sending files out to the cloud to be backed up. Bitrate, progress, time remaining all look right. The server version reported in the GUI is now saying 4.8, rather than 4.7, and there are no "upgrade failed" banners in the GUI.
So I don't know - doesn't look quite right to me - but seems to be working!
Nick