Dear Corinna,

ok the hint to the permission bits sounds reasonable. But I am a little bit confused, because the first modules that will be loaded are syslogformat and basicfuncs. After this the module afsocket will be loaded and produces errors.

The machines are standalone windows installations, no active directory and with admin privileges.

You also wrote about SIDs, which will be saved in etc directory. As I wrote before, I copied the installation to the server and back to the same machine and this did not work too. There could be two possibilities: windows registry and file privileges.

At first I wanted to copy only the syslog-ng.exe from usr/sbin to the other machine (includes the dlls of course). And then wanted to run the application standalone. Because this did not work, I copied the whole cygwin installation.
But I think I have to mail to the cygwin community.

If anybody has something for me, please let me know.


Bye Tom


2013/6/17 Tom Doberstein <t.doberstein@web.de>
Hello,

I am using syslog-ng in cygwin under WinXP.

On my developer pc I have no problems, everything works very fine. But when I copy the cygwin directory (from c:/Programs to c:/Programs) on another pc, I got the following errors:
-----------------
Error opening plugin module; module='afsocket', error='Exec format error'
Error opening plugin module; module='afsocket', error='Exec format error'
Error parsing source, source plugin unix-dgram not found in source confgen syste
m at line 1, column 1:
                                              included from /etc/syslog-ng/syslo
g-ng.conf line 10, column 9

unix-dgram
^^^^^^^^^^

yslog-ng
-----------------

I already started the syslog-ng-config and the service was installed successfully, but it will not start. cygrunsrv.exe -S syslog-ng will produce this error: "cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062: (...)".

Is there now any right problem that the process cannot read the module correctly or something else?
What I noticed is, when I copy the cygwin directory to the server and back to the same pc (in the same directory) the error occurs too.

I hope that somebody can help me with that problem.


Regards,
Tom