- syslog-ng - lists.balabit.hu

Continued struggle with getting shell env vars into log statements
by jetjnkr＠gmail.com 29 Sep '14

29 Sep '14

Greetings, I'm trying to get an environment variable (As defined in the shell - take for example "HOSTNAME"). echo $HOSTAME provides the expected string.... I then would like to append this to a set of messages based upon a specific destination. I'm using syslog-ng 3.2.5. In this case the 'hostname' is just an example, I know that the sending hostname is automatically prepended - used here because it's commonly defined on systems. I've included the following config lines from my syslog-ng.conf file. destination d_web_call { file("/var/log/web_call" template("<$PRI> $DATE $HOST $MSGHDR$MSG host=`HOSTNAME` \n") template_escape(no)); }; filter f_web_call { facility(local1) and ( match("^.*apache-call.*$" value("MSGHDR")) );}; log { source(s_sys); filter(f_web_call); destination (d_web_call); flags(final,flow-control); }; Using the following test string: /usr/bin/logger -t apache-call-tst -p local1.notice "This is a test message 25" I get the following: <141> Sep 26 17:21:18 lab.xxxx.com apache-call-tst: This is a test message25 host= I've received a few pointers from folks here (including going to 3.5 which can't be completed in the short term....). If tried things with 'define' and using the '$' but not back-tick for the shell variable. It is not clear when this value is set (if at all) within the config file. Thanks, Jim.

1 0

type hinting / mongodb / TAGS as array
by Lucas, Sascha 29 Sep '14

29 Sep '14

Hi, I'm again looking for a way to store patterndb classified / tagged events in mongodb. My greatest wish is to store the event tags as an array (list) in mongodb. This would greatly enhance querying for different combinations of tags. ATM TAGS is a string. According to the documentation, there seems no way to "type hint" that tags is an array. Or do I miss something? Thanks, Sascha. Aufsichtsratsvorsitzender: Herbert Vogel Geschäftsführung: Michael Krüger Sitz der Gesellschaft: Halle/Saale Registergericht: Amtsgericht Stendal | Handelsregister-Nr. HRB 208414 UST-ID-Nr. DE 158253683 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Empfänger sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder des Inhalts dieser Mail sind nicht gestattet. Diese Kommunikation per E-Mail ist nicht gegen den Zugriff durch Dritte geschützt. Die GISA GmbH haftet ausdrücklich nicht für den Inhalt und die Vollständigkeit von E-Mails und den gegebenenfalls daraus entstehenden Schaden. Sollte trotz der bestehenden Viren-Schutzprogramme durch diese E-Mail ein Virus in Ihr System gelangen, so haftet die GISA GmbH - soweit gesetzlich zulässig - nicht für die hieraus entstehenden Schäden.

2 4

Re: [syslog-ng] SOLVED: syslog-ng and python program destination constantly being restarted again and again
by Andrew Bell 26 Sep '14

26 Sep '14

Hi,. Thanks for the feedback. I actually figured out the reason as to why this was happening, and it had to do with syslog-ng referencing a the default python path on the system instead of the custom python path I've installed in my home directory ("python" alias pointed to "/usr/bin/python" instead of my "/home/bin/python" path). The custom python path had all the third-party libraries that my script depended on for execution, and so that was why syslog-ng kept sending all these /var/log/messages because it couldn't import the libraries and was using the wrong python instance (Used an strace command against syslog-ng in order to confirm this). So I specified the fully qualified path to my custom home python instance and now my script is working and staying up indefinitely as expected. I also fully qualified the one error exception path as well. ~Andrew -----Original Message----- From: syslog-ng-bounces(a)lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Sandor Geller Sent: Friday, September 26, 2014 3:49 AM To: syslog-ng(a)lists.balabit.hu Subject: Re: [syslog-ng] syslog-ng and python program destination constantly being restarted again and again Hi, The logs you quoted imply that your custom script keeps dying therefore syslog-ng keeps respawning it. Without seeing the whole script I'd assume that the original problem occurs in the code path where the script tries to forward logs and an expection gets raised (BTW not all exceptions are derived from the Exception class so the exception handler is a bit incomplete but let's put this aside for now). In the exception handler you're trying to open a file containing '~' without using os.path.expanduser() so you end up with an invalid filename which can't get opened. As this exception isn't handled the interpreter aborts the script. So you should eliminate the root cause why the script can't forward logs and also improve the exception handling. hth, Sandor On 09/26/2014 01:12 AM, Andrew Bell wrote: > Hello all, > > Wondering if someone could help me with an issue I've run into > recently regarding the program destination in syslog-ng and a python > script I wrote to automate parsing log events sent over from our Web > Application firewall. For some months now, the script and syslog-ng > configuration were working swimmingly but then things recently started > to stop working and now the script refuses to remain up and forwarding as expected. > > First, here is what and destination looks like in my syslog-ng conf. > The general flow here being ASM events are generated on the firewall > (for whatever purpose), they get sent over to syslog-ng and my python > script then parses these logs and sends them over to another server > running ElasticSearch using the python requests library. This takes > place within the context of an infinite loop in my script - wait for a > log event to come in, execute, go back to waiting, and so forth. > > /destination asm_post {/ > > / program("python -u /home/data/asm_logs/asmlogPost.py" > flush_lines(1) flags(no_multi_line));/ > > /};/ > > I've specified the following flags based off other help forums that > suggested this would help to address the stdin buffer flushing issue > sometimes encountered with syslog-ng and python scripts. There are no > filters being applied here. > > // > > /source(sn_asm);/ > > /destination(asm_post);/ > > Now, my asmLogPost.py script is setup to always read in standard input > through an infinite loop as various best practice syslog-ng sources > have recommended. Here's an excerpt of where the reading in happens - > encapsulated within the context of a try/exception clause: > > /try:/ > > / while 1:/ > > / line = sys.stdin.readline()/ > > / #...read in line log event, log event parsing and POSTing to > other box executes in context of infinite loop...after each POST, it > should go back and wait to read in the next line/ > > /Exception, e:/ > > / # ...exception handling block to catch any errors, write to a file.../ > > / f = open('~/ error.txt','ab')/ > > / f.write('Error happened, here are the details - %s\n'% str(e))/ > > / f.close()/ > > As was said earlier, this has all worked out fine and dandy for quite > some time (and I haven't made any alterations to my script for about a > month or so). But just recently, syslog-ng now appears to be caught in > a loop where it constantly stops, starts, and restarts my script > continuously such that it can't log anything anymore sufficiently. > Also the PID is constantly changing for my script whenever I do a ps > -aef command, which would indicate that a new instance is constantly > being spun up by syslog-ng. > > Not only that, but there apparently appear to be the following > messages sprouting up in /var/log/messages constantly as well which I > think is due to syslog-ng always restarting my script > > /Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is > it running? [Errno 2] No such file or directory/ > > /Sep 25 16:28:57 sysa03 abrt: detected unhandled Python exception in > '/home/data/asm_logs/asmlogPost.py'/ > > /Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is > it running? [Errno 2] No such file or directory/ > > /Sep 25 16:28:57 sysa03 abrt: detected unhandled Python exception in > '/home/data/asm_logs/asmlogPost.py'/ > > /Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is > it running? [Errno 2] No such file or directory/ > > /Sep 25 16:28:57 sysa03 abrt: detected unhandled Python exception in > '/home/data/asm_logs/asmlogPost.py'/ > > /Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is > it running? [Errno 2] No such file or directory/ > > /Sep 25 16:28:57 sysa03 abrt: detected unhandled Python exception in > '/home/data/asm_logs/asmlogPost.py'/ > > /Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is > it running? [Errno 2] No such file or directory/ > > /Sep 25 16:28:57 sysa03 abrt: detected unhandled Python exception in > '/home/data/asm_logs/asmlogPost.py'/ > > /Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is > it running? [Errno 2] No such file or directory/ > > /Sep 25 16:28:58 sysa03 abrt: detected unhandled Python exception in > '/home/data/asm_logs/asmlogPost.py'/ > > /Sep 25 16:28:58 sysa03 abrt: can't communicate with ABRT daemon, is > it running? [Errno 2] No such file or directory/ > > /Sep 25 16:28:58 sysa03 abrt: detected unhandled Python exception in > '/home/data/asm_logs/asmlogPost.py'/ > > /Sep 25 16:28:58 sysa03 abrt: can't communicate with ABRT daemon, is > it running? [Errno 2] No such file or directory/ > > But the thing is, there are no exceptions or error files being > generated by my script even though these messages seem to say this > happening...if there were, my script should catch this and write it > down. Besides, it did used to do this initially as I was developing my > script but it would never halt overall execution or cause syslog-ng to > tear it down, it would just write out to an error.txt file within the same directory. > > // > > Can anyone offer any insight here? I'll admit I'm not familiar with > how the ABRT daemon functions and if it and syslog-ng are somehow > related here or not. And I'm pretty confident that there's nothing > wrong with my script as I am able to execute its current version just > fine from a shell prompt - it can send over the log event and > everything parsed as expected with no errors. I'm kind of at a dead > end, going through my script and these log messages, trying to restart > syslog-ng to refresh, trying to place debug log statements before the > "while 1:" loop, trying to move the while 1: loop to be outside the > try/exception clause, but not much of this seems to be helping so far. > > Many Thanks, > > Andrew > > > > ______________________________________________________________________ > ________ Member info: > https://lists.balabit.hu/mailman/listinfo/syslog-ng > Documentation: > http://www.balabit.com/support/documentation/?product=syslog-ng > FAQ: http://www.balabit.com/wiki/syslog-ng-faq > ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq

1 0

syslog-ng 3.6.0rc1 has been released
by devel＠balabit.hu 26 Sep '14

26 Sep '14

------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.6.0rc1 SUMMARY : new release candidate DATE : Sep 26, 2014 ------------------------------------------------------------------------------ DESCRIPTION: A new release candidate of syslog-ng Open Source Edition (3.6.0rc1) has been released. CHANGES: 3.6.0rc1 ======== Fri, 26 Sep 2014 11:17:31 +0200 This is the first Release Candidate of the syslog-ng OSE 3.6 branch. Based on our test results this release is almost production ready. Features -------- * Added groupset rewrite object. Groupset allows the user to modify multiple log message properties at once. It also allows referencing the old value of the property as the $_ macro. Bugfixes -------- * Fixed a memory leak during configuration parsing when using `rewrite()`. * Change control socket message from notice to debug * Fixes for retries() functionality. Retry counter incremented by every message write error (including network connection errors) which can lead to message lost. Credits ------- syslog-ng is developed as a community project, and as such it relies on volunteers, to do the work necessary to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. We would like to thank the following people for their contribution: Balazs Scheidler, Brian De Wolf, Gergely Nagy, Laszlo Budai, Peter Czanik, Tibor Benke, Viktor Juhasz, Viktor Tusa. DOWNLOAD: You can download the source or binary packages from: http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.6.0r… The documentation of the syslog-ng Open Source Edition is available in The syslog-ng Open Source Edition Administrator's Guide at http://www.balabit.com/support/documentation/

1 0

Re: [syslog-ng] Injecting environment variables?
by jetjnkr＠gmail.com 26 Sep '14

26 Sep '14

Ok sorry, but still struggling a bit with this: Running with the following version syslog-ng 3.2.5 Installer-Version: 3.2.5 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.2#master#9d4bea28198bd731df1a61e980a2af5b88d81116 Compile-Date: Jan 15 2012 19:47:30 Enable-Threads: on Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: off Enable-SQL: on Enable-Linux-Caps: off Enable-Pcre: on Enable-Pacct: off I've attempted a number of variations - all have made me sad..... template t_cust { template("CUST $CUST"); }; destination d_web_call { file("/var/log/web_call" template("<$PRI> $DATE $HOST $MSG template($t_cust) \n") template_escape(no)); }; or 'backtick'.... destination d_web_call { file("/var/log/web_call" template("<$PRI> $DATE $HOST $MSG `$CUST` \n") template_escape(no)); }; or... destination d_web_call { file("/var/log/web_call" template("<$PRI> $DATE $HOST $MSG Template("template $CUST")` \n") template_escape(no)); }; $CUST is definitely defined in the environment but the logs don't have any value appended.... Any further guidance appreciated.... On Sep 23, 2014, at 6:00 AM, syslog-ng-request(a)lists.balabit.hu wrote: > ---------------------- > > Message: 1 > Date: Mon, 22 Sep 2014 20:10:17 +0200 > From: Balazs Scheidler <bazsi77(a)gmail.com> > Subject: Re: [syslog-ng] Injecting environment variables? > To: "Syslog-ng users' and developers' mailing list" > <syslog-ng(a)lists.balabit.hu> > Message-ID: > <CAKcfE+a8ohm9rbAjyiBbHSs37iyE_mdP=SRU_Cgz_BSAccFFBg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > It came in with blocks and scl support. So if your version has support for > the system driver it will support this as well. My memories are vague with > 3.2. > > Environment variables are resolved at parsing time and should work like > this: > > Template("template ?envvar?") > > It works as if the environment variable was right there in the config file. > On Sep 21, 2014 3:14 PM, <jetjnkr(a)gmail.com> wrote: > >> Balazs, >> >> Thanks, do you have any examples in using the backtick it in a message >> template? Do you have to assign it to a config variable in a "define" >> first? >> >> How much 'earlier' versions of syslog-ng will this work (e.g. before 3.2 >> ?) >> >> Jim. >> >> >>> >>> >>> From: Balazs Scheidler <bazsi77(a)gmail.com> >>> Subject: Re: [syslog-ng] Injecting environment variables? >>> To: "Syslog-ng users' and developers' mailing list" >>> <syslog-ng(a)lists.balabit.hu>, wernli(a)in2p3.fr >>> Message-ID: >>> < >> CAKcfE+ZKqqPnPOOSJek81eq_EPa7y3jUrPyKYH94jc3mxvPsmg(a)mail.gmail.com> >>> Content-Type: text/plain; charset="utf-8" >>> >>> Earlier you could use the backtick env variable format. >>> >>> This one is substituted at config parsing. >>> On Sep 18, 2014 5:26 PM, "Fabien Wernli" <wernli(a)in2p3.fr> wrote: >>> >>>> Hi Jim, >>>> >>>> As of version 3.5 you can use the `env` template function: >>>> >>>> template("<$PRI> $DATE $HOST $MSG $(env <environment-variable>) \n") >>>> template_escape(no)); >>>> >>>> Cheers >>>> >>>> >>>> >> ______________________________________________________________________________ >>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>> Documentation: >>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>> >>>> >>>

2 1

syslog-ng and python program destination constantly being restarted again and again
by Andrew Bell 26 Sep '14

26 Sep '14

Hello all, Wondering if someone could help me with an issue I've run into recently regarding the program destination in syslog-ng and a python script I wrote to automate parsing log events sent over from our Web Application firewall. For some months now, the script and syslog-ng configuration were working swimmingly but then things recently started to stop working and now the script refuses to remain up and forwarding as expected. First, here is what and destination looks like in my syslog-ng conf. The general flow here being ASM events are generated on the firewall (for whatever purpose), they get sent over to syslog-ng and my python script then parses these logs and sends them over to another server running ElasticSearch using the python requests library. This takes place within the context of an infinite loop in my script - wait for a log event to come in, execute, go back to waiting, and so forth. destination asm_post { program("python -u /home/data/asm_logs/asmlogPost.py" flush_lines(1) flags(no_multi_line)); }; I've specified the following flags based off other help forums that suggested this would help to address the stdin buffer flushing issue sometimes encountered with syslog-ng and python scripts. There are no filters being applied here. source(sn_asm); destination(asm_post); Now, my asmLogPost.py script is setup to always read in standard input through an infinite loop as various best practice syslog-ng sources have recommended. Here's an excerpt of where the reading in happens - encapsulated within the context of a try/exception clause: try: while 1: line = sys.stdin.readline() #...read in line log event, log event parsing and POSTing to other box executes in context of infinite loop...after each POST, it should go back and wait to read in the next line Exception, e: # ...exception handling block to catch any errors, write to a file... f = open('~/ error.txt','ab') f.write('Error happened, here are the details - %s\n'% str(e)) f.close() As was said earlier, this has all worked out fine and dandy for quite some time (and I haven't made any alterations to my script for about a month or so). But just recently, syslog-ng now appears to be caught in a loop where it constantly stops, starts, and restarts my script continuously such that it can't log anything anymore sufficiently. Also the PID is constantly changing for my script whenever I do a ps -aef command, which would indicate that a new instance is constantly being spun up by syslog-ng. Not only that, but there apparently appear to be the following messages sprouting up in /var/log/messages constantly as well which I think is due to syslog-ng always restarting my script Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory Sep 25 16:28:57 sysa03 abrt: detected unhandled Python exception in '/home/data/asm_logs/asmlogPost.py' Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory Sep 25 16:28:57 sysa03 abrt: detected unhandled Python exception in '/home/data/asm_logs/asmlogPost.py' Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory Sep 25 16:28:57 sysa03 abrt: detected unhandled Python exception in '/home/data/asm_logs/asmlogPost.py' Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory Sep 25 16:28:57 sysa03 abrt: detected unhandled Python exception in '/home/data/asm_logs/asmlogPost.py' Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory Sep 25 16:28:57 sysa03 abrt: detected unhandled Python exception in '/home/data/asm_logs/asmlogPost.py' Sep 25 16:28:57 sysa03 abrt: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory Sep 25 16:28:58 sysa03 abrt: detected unhandled Python exception in '/home/data/asm_logs/asmlogPost.py' Sep 25 16:28:58 sysa03 abrt: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory Sep 25 16:28:58 sysa03 abrt: detected unhandled Python exception in '/home/data/asm_logs/asmlogPost.py' Sep 25 16:28:58 sysa03 abrt: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory But the thing is, there are no exceptions or error files being generated by my script even though these messages seem to say this happening...if there were, my script should catch this and write it down. Besides, it did used to do this initially as I was developing my script but it would never halt overall execution or cause syslog-ng to tear it down, it would just write out to an error.txt file within the same directory. Can anyone offer any insight here? I'll admit I'm not familiar with how the ABRT daemon functions and if it and syslog-ng are somehow related here or not. And I'm pretty confident that there's nothing wrong with my script as I am able to execute its current version just fine from a shell prompt - it can send over the log event and everything parsed as expected with no errors. I'm kind of at a dead end, going through my script and these log messages, trying to restart syslog-ng to refresh, trying to place debug log statements before the "while 1:" loop, trying to move the while 1: loop to be outside the try/exception clause, but not much of this seems to be helping so far. Many Thanks, Andrew

2 1

Re: [syslog-ng] Injecting environment variables?
by jetjnkr＠gmail.com 22 Sep '14

22 Sep '14

Balazs, Thanks, do you have any examples in using the backtick it in a message template? Do you have to assign it to a config variable in a "define" first? How much 'earlier' versions of syslog-ng will this work (e.g. before 3.2 ?) Jim. > > > From: Balazs Scheidler <bazsi77(a)gmail.com> > Subject: Re: [syslog-ng] Injecting environment variables? > To: "Syslog-ng users' and developers' mailing list" > <syslog-ng(a)lists.balabit.hu>, wernli(a)in2p3.fr > Message-ID: > <CAKcfE+ZKqqPnPOOSJek81eq_EPa7y3jUrPyKYH94jc3mxvPsmg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Earlier you could use the backtick env variable format. > > This one is substituted at config parsing. > On Sep 18, 2014 5:26 PM, "Fabien Wernli" <wernli(a)in2p3.fr> wrote: > >> Hi Jim, >> >> As of version 3.5 you can use the `env` template function: >> >> template("<$PRI> $DATE $HOST $MSG $(env <environment-variable>) \n") >> template_escape(no)); >> >> Cheers >> >> >> ______________________________________________________________________________ >> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >> Documentation: >> http://www.balabit.com/support/documentation/?product=syslog-ng >> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >> >> >

2 1

Re: [syslog-ng] syslog-ng Digest, Vol 113, Issue 9
by jetjnkr＠gmail.com 20 Sep '14

20 Sep '14

Hi Famien, Thanks - just need to get the Ops team to push out 3.5 and I'll give it a shot! Jim. On Sep 19, 2014, at 2:46 AM, syslog-ng-request(a)lists.balabit.hu wrote: > > Date: Thu, 18 Sep 2014 17:26:33 +0200 > From: Fabien Wernli <wernli(a)in2p3.fr> > Subject: Re: [syslog-ng] Injecting environment variables? > To: "Syslog-ng users' and developers' mailing list" > <syslog-ng(a)lists.balabit.hu> > Message-ID: <20140918152633.GC6867(a)ccfawe.in2p3.fr> > Content-Type: text/plain; charset=us-ascii > > Hi Jim, > > As of version 3.5 you can use the `env` template function: > > template("<$PRI> $DATE $HOST $MSG $(env <environment-variable>) \n") template_escape(no)); > > Cheers > > >

1 0

Injecting environment variables?
by jetjnkr＠gmail.com 20 Sep '14

20 Sep '14

New to the list, but looking for some pointers: It is possible to get shell variables interpreted and defined in the context of the syslog-ng.conf file? I'm trying to get the value from a shell/environment variable to be added to a logged message. I've tried various forms of templates in the destination without much success. template("<$PRI> $DATE $HOST $MSG $someENVvar \n") template_escape(no)); Static text works find, but the var ends up being blank... For reasons I won't belabor, I can't use tags as added by the source. Apologies if this has been covered previous - I didn't see anything from scanning the archives. Thanks. Jim.

3 2

classify/assign events to tenants/customers
by Lucas, Sascha 19 Sep '14

19 Sep '14

Hi, I'm looking for a way to "classify"/assign events to tenants/customers. A tenant/customer can be all events belonging to host or a combination of host/program. I thought patterndb can help doing this. However it seems there is no way? * classification: pattern is per program and limited to the message * correlation: context is limited to one host not many Do I miss something, or are there even better ways? Thanks, Sascha. Aufsichtsratsvorsitzender: Herbert Vogel Geschäftsführung: Michael Krüger Sitz der Gesellschaft: Halle/Saale Registergericht: Amtsgericht Stendal | Handelsregister-Nr. HRB 208414 UST-ID-Nr. DE 158253683 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Empfänger sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder des Inhalts dieser Mail sind nicht gestattet. Diese Kommunikation per E-Mail ist nicht gegen den Zugriff durch Dritte geschützt. Die GISA GmbH haftet ausdrücklich nicht für den Inhalt und die Vollständigkeit von E-Mails und den gegebenenfalls daraus entstehenden Schaden. Sollte trotz der bestehenden Viren-Schutzprogramme durch diese E-Mail ein Virus in Ihr System gelangen, so haftet die GISA GmbH - soweit gesetzlich zulässig - nicht für die hieraus entstehenden Schäden.

3 3