Node Install fails on SuSE 12

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install node instance on SuSE 12.1
2. syslog-ng.service never starts; syslog-ng.service doesn't exist on the system

What is the expected output? What do you see instead?
I would expect syslog-ng to start normally, but it does not.
Perhaps this problem arises as older SuSEs don't use systemd?

What version of the product are you using? On what operating system?
Latest SVN 936 -- openSuSE x86_64 12

Please provide any additional information below.
If you need a custom syslog-ng.service file, I can write one. I just need some 
info to coordinate with you.

Install log is attached

Original issue reported on code.google.com by i...@pingas.org on 25 Jun 2013 at 8:18

[GoogleCodeExporter]

Erm... It didn't seem to attach my file so let me try again.

Original comment by i...@pingas.org on 25 Jun 2013 at 8:19

Attachments:

• elsa-suse-install-log.txt

[GoogleCodeExporter]

I'm working on openSUSE 12 right now, and it seems to have a problem even 
getting MySQL running after being installed.  Did MySQL install?  Are you able 
to start it?  It appears to have installed and started just fine, based on your 
log, so I'm confused as to why it's not working on my minimal install.  I'm 
trying on openSuSE 12.3.  Is that the version you're using?  If you have a 
working syslog-ng.service file, that would be great.

Original comment by mchol...@gmail.com on 25 Jun 2013 at 10:07

[GoogleCodeExporter]

MySQL installed and is set to auto-start.

The proper commands to enable it to boot and start it on openSuSE 12 are:
systemctl start mysql.service && systemctl enable mysql.service
They're not native services right there, but I'm sure openSuSE will make the 
switch to native systemd for those packages soon.

As for syslog-ng, the service file probably looks like this (though you need to 
fill in the full path to the config file):

[Unit]
Description=System Logger Daemon
Documentation=man:syslog-ng(8)
Requires=var-run.mount syslog.target
After=var-run.mount

[Service]
Sockets=syslog.socket
ExecStart=/usr/local/syslog-ng/sbin/syslog-ng -F -f /path/to/config.conf
ExecReload=/bin/kill -HUP $MAINPID
StandardOutput=null
Restart=on-failure

[Install]
WantedBy=multi-user.target
Alias=syslog.service

Original comment by i...@pingas.org on 27 Jun 2013 at 2:27

[GoogleCodeExporter]

Just replace /path/to/config.conf with /usr/local/syslog-ng/etc/syslog-ng.conf 
and it works! Needs a little tweaking as the systemd environment for suse is 
different than archlinux's enviroment, but at least it starts properly!

systemctl status syslog-ng.service
syslog-ng.service - System Logger Daemon
      Loaded: loaded (/etc/systemd/system/syslog-ng.service; enabled)
      Active: active (running) since Thu, 2013-06-27 10:34:12 EDT; 3s ago
        Docs: man:syslog-ng(8)
    Main PID: 4364 (syslog-ng)
      CGroup: name=systemd:/system/syslog-ng.service
          ├ 4364 /usr/local/syslog-ng/sbin/syslog-ng -F -f /usr/local/syslog-ng/etc/syslog-ng.conf
          ├ 4365 perl /usr/local/elsa/node/elsa.pl -c /etc/elsa_node.conf -f __OPS__
          ├ 4366 perl /usr/local/elsa/node/elsa.pl -c /etc/elsa_node.conf
          ├ 4367 perl /usr/local/elsa/node/elsa.pl -c /etc/elsa_node.conf -f __IMPORT__
          └ 4422 /usr/local/sphinx/bin/indexer --config /usr/local/etc/sphinx.conf --rotate perm_8

Jun 27 10:34:12 susniff.helmpoint.com systemd[1]: Starting System Logger 
Daemon...
Jun 27 10:34:12 susniff.helmpoint.com systemd[1]: Started System Logger Daemon.

Original comment by i...@pingas.org on 27 Jun 2013 at 2:35