[systemd-devel] java crashes only on boot

[Florian Lindner]

Andrei Borzenkov wrote:

> В Sun, 21 Dec 2014 21:24:22 +0100
> Florian Lindner <mailinglists at xgm.de> пишет:
> 
>> 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
>> # /usr/lib/systemd/system/crashplan.service
>> [Unit]
>> Description=CrashPlan Backup Engine
>> After=network.target
>> 
> 
> Does it depend on network? In this case network may not yet be
> available; you may try to use network-online.target instead.

I don't think it depends on having actual network access. I tried using 
network-online.target but changed nothing.
 
>> [Service]
>> 
>> Type=forking
>> PIDFile=/opt/crashplan/CrashPlanEngine.pid
>> EnvironmentFile=/opt/crashplan/bin/run.conf
>> WorkingDirectory=/opt/crashplan
>> ExecStart=/opt/crashplan/bin/CrashPlanEngine start
>> ExecStop=/opt/crashplan/bin/CrashPlanEngine stop
>> 
>> [Install]
>> WantedBy=multi-user.target
>> 
>> 
>> 
>> % systemctl --version
>> systemd 218
>> +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP
>> +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN
>> 
>> 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
>> 
>> _______________________________________________
>> systemd-devel mailing list
>> systemd-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> 
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel