You are not logged in.
Hello,
on my up to date Arch system I use Crashplan which is a java app for offsite backups. It used to work fine, until recently...
When booting java dumps core:
# systemctl status crashplan.service
● crashplan.service - CrashPlan Backup Service
Loaded: loaded (/etc/systemd/system/crashplan.service; enabled; vendor preset: disabled)
Active: failed (Result: signal) since So 2014-12-21 20:00:59 CET; 58s ago
Process: 464 ExecStop=/opt/crashplan/bin/CrashPlanEngine stop (code=exited, status=0/SUCCESS)
Process: 349 ExecStart=/opt/crashplan/bin/CrashPlanEngine start (code=exited, status=0/SUCCESS)
Main PID: 366 (code=killed, signal=ABRT)
Dez 21 20:00:48 horus CrashPlanEngine[349]: Starting CrashPlan Engine ... Using standard startup
Dez 21 20:00:48 horus CrashPlanEngine[349]: OK
Dez 21 20:00:48 horus systemd[1]: Started CrashPlan Backup Service.
Dez 21 20:00:49 horus systemd[1]: crashplan.service: main process exited, code=killed, status=6/ABRT
Dez 21 20:00:49 horus CrashPlanEngine[464]: Stopping CrashPlan Engine ... /opt/crashplan/bin/CrashPlanEngine: Zeile 144: kill: (366) - Kein passender Prozess gefunden
Dez 21 20:00:50 horus systemd-coredump[459]: Process 366 (java) of user 0 dumped core.
Dez 21 20:00:59 horus CrashPlanEngine[464]: OK
Dez 21 20:00:59 horus systemd[1]: Unit crashplan.service entered failed state.
Dez 21 20:00:59 horus systemd[1]: crashplan.service failed.
# systemctl cat crashplan.service
# /etc/systemd/system/crashplan.service
[Unit]
Description=CrashPlan Backup Service
After=local-fs.target network.target
[Service]
ExecStart=/opt/crashplan/bin/CrashPlanEngine start
ExecReload=/opt/crashplan/bin/CrashPlanEngine reload
ExecStop=/opt/crashplan/bin/CrashPlanEngine stop
Type=forking
WorkingDirectory=/opt/crashplan
PIDFile=/opt/crashplan/CrashPlanEngine.pid
EnvironmentFile=/opt/crashplan/bin/run.conf
[Install]
WantedBy=multi-user.target
But when I start it manually with systemctl start crashplan.service it works fine.
I got no idea where to look for clues...
Thanks,
Florian
Offline
Hello Florian,
I'm experiencing the same issue, but with the crashplan enterprise pro version.
I've linked to this thread in a new comment here: https://aur.archlinux.org/packages/crashplan/
Hopefully someone can track down what's happening.
"There's a special place in hell...
... reserved for child molesters and people who talk in the theater."
-- Shepherd Meriah Book, "Firefly"
Offline
That fix is related to the UI component, it's the daemon that crashes. The fix proposed is about some SWT issue, which is a Java GUI toolkit.
BTW, for me it runs fine with the line
ExecStartPre=/usr/bin/sleep 10
added to the [Service] part of the unit file.
Last edited by Osiris (2015-01-05 21:59:47)
Offline