Skip to content

condor.service Fails to Start Automatically on COMET Nodes #18

@vahid-dan

Description

@vahid-dan

Error log:

● condor.service - LSB: Manage condor daemons
   Loaded: loaded (/etc/init.d/condor; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2017-05-24 07:02:34 PDT; 10min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1185 ExecStart=/etc/init.d/condor start (code=exited, status=1/FAILURE)

May 24 07:02:32 comet-W2 systemd[1]: Starting LSB: Manage condor daemons...
May 24 07:02:34 comet-W2 condor[1185]: mkdir: cannot create directory ‘FATAL: Unable to locate LOG in /etc/condor/condor_config’: No such file 
May 24 07:02:34 comet-W2 condor[1185]: chown: cannot access 'FATAL: Unable to locate LOG in /etc/condor/condor_config': No such file or directo
May 24 07:02:34 comet-W2 condor[1185]: FATAL: Required directory FATAL: Unable to locate LOG in /etc/condor/condor_config does not exist, or is
May 24 07:02:34 comet-W2 systemd[1]: condor.service: Control process exited, code=exited status=1
May 24 07:02:34 comet-W2 systemd[1]: Failed to start LSB: Manage condor daemons.
May 24 07:02:34 comet-W2 systemd[1]: condor.service: Unit entered failed state.
May 24 07:02:34 comet-W2 systemd[1]: condor.service: Failed with result 'exit-code'.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions