- syslog-ng - lists.balabit.hu

Insider 2016-11: Enrichment; Elasticsearch; LISA; FreeBSD; All Things Open;
by Czanik, Péter 11 Nov '16

11 Nov '16

Dear syslog-ng users, This is the 52nd issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS Enriching log messages ---------------------- Log messages already contain a wealth of information about what is happening in your systems. Still, logs can be enriched with additional information – like the geolocation belonging to an IP address – which can improve the usability of logs considerably. Read how you can enrich log messages in real-time using syslog-ng at https://www.balabit.com/blog/enriching-log-messages-with-additional-informa… What is new in syslog-ng PE and SSB ----------------------------------- Join us at our next webinar on November 15, where you can learn about new syslog-ng PE and SSB features like content-based alerting, multiple log spaces, key=value parser and Big Data destinations. You can register at http://go.balabit.com/q9VU0A0F5l0E7Q03Z0zY00T Logging to Elasticsearch simplified ----------------------------------- Elasticsearch is gaining the momentum as the ultimate destination for log messages. A great part of it is Kibana, but also that it is a scalable storage of arbitrary name-value pairs. Read, how the use of syslog-ng can greatly simplify how logs reach Elasticsearch: https://www.balabit.com/blog/logging-to-elasticsearch-made-simple-with-sysl… Coming up: LISA --------------- You can learn about syslog-ng at the Balabit booth #145 at LISA (Large Installation System Administration) conference in Boston. Expo days are on December 7 and 8: https://www.usenix.org/conference/lisa16/expo syslog-ng with Java support on FreeBSD -------------------------------------- Java destinations on FreeBSD are not supported by the syslog-ng team and for technical reasons (it downloads JAR files from the Internet) it is also marked broken in FreeBSD ports. Luckily it does not prevent it from working: some people even use it it production. Learn, how to get started at https://www.balabit.com/blog/test-the-latest-freebsd-with-syslog-ng-3-8-1/ All Things Open --------------- Last week I visited All Things Open, one of the largest open source conferences of the US East Coast. I was presenting syslog-ng in the Operations track of the conference, but luckily I had a chance to stay for the full two days of the event. Read my experiences at: TBD Your feedback and news, or tips about the next issue are welcome at documentation(a)balabit.com. To read this newsletter online, visit: https://syslog-ng.org/ Peter Czanik (CzP) <peter.czanik(a)balabit.com> Balabit / syslog-ng upstream https://www.balabit.com/blog/author/peterczanik/ https://twitter.com/PCzanik

1 1

Syslog-ng 3.7.2 install fails on U12.04
by Varugis Kurien 10 Nov '16

10 Nov '16

When installing from the repository here (http://download.opensuse.org/repositories/home:/laszlo_budai:/syslog-ng/xUb…) the install fails to install syslog-ng3.7.2 with the message: rm_conffile voodoo unsupported for package syslog-ng-mod-python! -- This appears to be coming when installing syslog-ng-mod-python due to a failure in a preinstallation script. How can I fix this?

1 1

Possible elementary question
by Varugis Kurien 10 Nov '16

10 Nov '16

I'm having some conniptions doing central logging using syslog-ng. Here is the scenario: 1. I generate logs using syslog-ng on local servers and then send them to a log-destination server. Here is an example of some of the conf files on the generating server: more iptables.log.conf source s_var_log_iptables.log { file("/var/log/iptables.log" program-override(var_log_iptables.log) flags(no-parse)); }; log { source(s_var_log_iptables.log); destination(d_midfin_logger_2); }; more midfin_logger_2.conf template t_sdx_tagged { template("$ISODATE $HOST $PROGRAM $MSG "); template_escape(no); }; destination d_midfin_logger_2 { tcp( "10.4.16.161" port(514) template(t_sdx_tagged)); }; What I am trying to do on the log host is to: 1. Segregate at the top level by host. For each such host: * Split the logs into different directories so that for example, I'll have one directory for the audit log from that host, another for iptables etc - so that under each host I'll have /var/log/iptables.log etc. I've been unable to grok the documentation to figure out quite how to do this and would really appreciate some help. thanks vk ==

3 3

linux-audit-parser not found on stock install of Ubuntu 16.04
by Varugis Kurien 02 Nov '16

02 Nov '16

When using a freshly installed version of U16.04, I found that the linux audit log parser does not seem to be installed. For example: syslog-ng --module-registry|grep audit <-- returns nothing == 1. This started because I experienced a failure when trying to enable the linux audit parser: Error parsing parser expression, parser plugin linux-audit-parser not found in /etc/syslog-ng/conf.d/auditd.log.conf at line 3, column 8: included from /etc/syslog-ng/syslog-ng.conf line 164, column 1 linux-audit-parser(prefix(".auditd.")); 2. The corresponding conf file is below: source s_var_log_audit.log { file("/var/log/audit/audit.log" flags(no-parse)); }; parser p_audit_syslog_parser { linux-audit-parser(prefix(".auditd.")); }; log { source(s_var_log_audit.log); parser(p_audit_syslog_parser); destination(d_midfin_logger_2); }; The officially supported version of syslog-ng in ubuntu is 3.5.1. == syslog-ng 3.5.6 Installer-Version: 3.5.6 Revision: 3.5.6-2.1 [@416d315] (Ubuntu/16.04) Compile-Date: Oct 24 2015 03:49:19 Available-Modules: json-plugin,csvparser,system-source,tfgeoip,afsocket-notls,afamqp,basicfuncs,affile,afsocket-tls,dbparser,afmongodb,cryptofuncs,afsmtp,linux-kmsg-format,afuser,redis,afsocket,afstomp,sysl\ ogformat,confgen,afprog,afsql Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-Linux-Caps: on Enable-Pcre: on Do I need to install an unofficial version or is there some elementary mistake that I am making. thanks Varugis

2 1

Feedback test
by Scheidler, Balázs 27 Oct '16

27 Oct '16

Hi, The README.md file visible on github advertises this email address that is forwarded to the mailing list. This is a test and shows if the forwarding works properly -- Bazsi

1 0

Fwd: syslog-ng 3.7.3 crashing randomly
by Soumyadip Das Mahapatra 25 Oct '16

25 Oct '16

Hi, We have installed syslog-ng 3.7.3 on RHEL 6.6 from COPR repo: >From dmesg: [Thu Sep 1 02:24:08 2016] syslog-ng[10374]: segfault at 1a116c10 ip 000000001a116c10 sp 00007f26eebfa928 error 15 [Sun Sep 4 20:10:47 2016] syslog-ng[27797]: segfault at 0 ip (null) sp 00007f998b5fb928 error 14 in syslog-ng[400000+3000] [Mon Sep 5 19:04:15 2016] syslog-ng[12727]: segfault at 36aaa42080 ip 00000039b8618df0 sp 00007f996fffc878 error 7 in libglib-2.0.so.0.2800.8[ 39b8600000+115000] [Tue Sep 6 03:01:21 2016] syslog-ng[3827]: segfault at 15cb09d0 ip 0000000015cb09d0 sp 00007f99aebfa928 error 15 [Fri Sep 9 05:03:41 2016] syslog-ng[28275] general protection ip:39b8618df0 sp:7f29c57f8878 error:0 in libglib-2.0.so.0.2800.8[ 39b8600000+115000] [Sun Sep 11 00:48:01 2016] syslog-ng[14479]: segfault at 0 ip (null) sp 00007f2a03caf928 error 14 in syslog-ng[400000+3000] [Sun Sep 11 10:15:37 2016] syslog-ng[2012]: segfault at 0 ip 00000036aaa3cc1c sp 00007feed2bfa880 error 6 in libsyslog-ng-3.7.so.0.0.0[ 36aaa00000+a2000] Core 1: (gdb) bt full #0 0x00000039b8618df0 in g_atomic_int_add () from /lib64/libglib-2.0.so.0 No symbol table info available. #1 0x00000036aaa3cbe4 in stats_counter_add (self=0xabe68ea0, thread_id=5) at lib/stats/stats-counter.h:39 No locals. #2 log_queue_fifo_move_input_unlocked (self=0xabe68ea0, thread_id=5) at lib/logqueue-fifo.c:193 queue_len = 1755882337 #3 0x00000036aaa3cd6e in log_queue_fifo_move_input (user_data=0xabe68ea0) at lib/logqueue-fifo.c:215 self = 0xabe68ea0 thread_id = 5 __PRETTY_FUNCTION__ = "log_queue_fifo_move_input" #4 0x00000036aaa456ca in main_loop_worker_invoke_batch_callbacks () at lib/mainloop-worker.c:270 cb = 0xabe690e0 lh = 0xabe690e0 lh2 = 0xabe690e0 #5 0x00000036aaa6fa2a in iv_work_thread_do_work (_thr=0x9d6bd530) at iv_work.c:118 work = 0x6fb160 thr = 0x9d6bd530 pool = 0x6e48c0 last_seq = 1477269410 #6 0x00000036aaa6ed4a in iv_run_tasks (st=0x7f29b44d3c00) at iv_task.c:48 t = <value optimized out> tasks = {next = 0x7f29c57f89a0, prev = 0x7f29c57f89a0} #7 0x00000036aaa7100c in iv_main () at iv_main_posix.c:106 to = {tv_sec = 10, tv_nsec = 0} st = 0x7f29b44d3c00 #8 0x00000036aaa6f841 in iv_work_thread (_thr=0x9d6bd530) at iv_work.c:200 thr = 0x9d6bd530 pool = 0x6e48c0 #9 0x00000036aaa71a1f in iv_thread_handler (_thr=0x75242f90) at iv_thread_posix.c:142 __clframe = {__cancel_routine = 0x36aaa71a80 <iv_thread_cleanup_handler>, __cancel_arg = 0x75242f90, __do_it = 1, __cancel_type = 0} thr = 0x75242f90 #10 0x00000039b6e079d1 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. #11 0x00000039b6ae88fd in clone () from /lib64/libc.so.6 No symbol table info available. Core 2: (gdb) bt full #0 0x0000000000000000 in ?? () No symbol table info available. #1 0x00000036aaa456ca in main_loop_worker_invoke_batch_callbacks () at lib/mainloop-worker.c:270 cb = 0x87e96b10 lh = 0x87e96b10 lh2 = 0x0 #2 0x00000036aaa6fa2a in iv_work_thread_do_work (_thr=0x7034ffd0) at iv_work.c:118 work = 0x6fb390 thr = 0x7034ffd0 pool = 0x6e48b0 last_seq = 1323426114 #3 0x00000036aaa6ed4a in iv_run_tasks (st=0x7f29d4360200) at iv_task.c:48 t = <value optimized out> tasks = {next = 0x7f2a03caf9a0, prev = 0x7f2a03caf9a0} #4 0x00000036aaa7100c in iv_main () at iv_main_posix.c:106 to = {tv_sec = 10, tv_nsec = 0} st = 0x7f29d4360200 #5 0x00000036aaa6f841 in iv_work_thread (_thr=0x7034ffd0) at iv_work.c:200 thr = 0x7034ffd0 pool = 0x6e48b0 #6 0x00000036aaa71a1f in iv_thread_handler (_thr=0x426b490) at iv_thread_posix.c:142 __clframe = {__cancel_routine = 0x36aaa71a80 <iv_thread_cleanup_handler>, __cancel_arg = 0x426b490, __do_it = 1, __cancel_type = 0} thr = 0x426b490 #7 0x00000039b6e079d1 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. #8 0x00000039b6ae88fd in clone () from /lib64/libc.so.6 No symbol table info available. So looks like segfault is happening at random part of the code. # cat /etc/sysconfig/syslog-ng #--- # Syslog-ng command line options # See syslog-ng(8) for more details #--- SYSLOGNG_PID="/var/run/syslog-ng.pid" SYSLOGNG_OPTIONS="-p $SYSLOGNG_PID --fd-limit 30000" SYSLOGNG_COMPAT_PID="/var/run/syslogd.pid" # cat /etc/syslog-ng/syslog-ng.conf @version:3.6 options { flush_lines (0); time_reopen (10); log_fifo_size (20000); use_dns (yes); use_fqdn (yes); create_dirs (yes); dir_group("wheel"); dir_owner("nobody"); dir_perm(0755); owner("nobody"); group("nobody"); perm(0644); threaded(yes); keep_hostname (yes); chain_hostnames(yes); bad_hostname("[^[:print:]]"); dns_cache(yes); dns_cache_expire(300); dns_cache_expire_failed(30); dns_cache_size(1000); stats_freq(3600); flush_lines(0); }; source s_sys { file ("/proc/kmsg" program_override("kernel: ")); unix-stream ("/dev/log"); # udp(ip(0.0.0.0) port(514)); }; source s_tcp { network(transport("tcp") port(514) so_rcvbuf(8388608) max-connections(200) log-iw-size(20000)); }; source s_udp { network(transport("udp") port(514) so_rcvbuf(8388608) log-iw-size(20000)); }; source s_net { network(transport("udp") port(515) so_rcvbuf(8388608) log-iw-size(20000) tags("source_net")); network(transport("tcp") port(515) so_rcvbuf(8388608) max-connections(200) log-iw-size(20000) tags("source_net")); }; source s_windows { network(transport("tcp") port(516) so_rcvbuf(8388608) max-connections(200) log-iw-size(20000) tags("windows")); }; destination d_cons { file("/dev/console"); }; destination d_mesg { file("/var/log/messages"); }; destination d_auth { file("/var/log/secure"); }; destination d_mail { file("/var/log/maillog" flush_lines(10)); }; destination d_spol { file("/var/log/spooler"); }; destination d_boot { file("/var/log/boot.log"); }; destination d_cron { file("/var/log/cron"); }; destination d_kern { file("/var/log/kern"); }; destination d_mlal { usertty("*"); }; destination d_userx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/user.log"); }; destination d_kernx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/kern.log"); }; destination d_mailx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/mail.log"); }; destination d_mp { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/mp.log"); }; destination d_daemonx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/daemon.log"); }; destination d_authx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/auth.log"); }; destination d_lprx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/lpr.log"); }; destination d_cronx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/cron.log"); }; destination d_messagesx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/messages.log"); }; destination d_networkx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/network.log"); }; destination d_firewallx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/firewall.log"); }; destination d_local0 { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/sp.log"); }; destination d_local1 { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/app.log"); }; destination d_localx { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/local.log"); }; destination d_local6 { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/httpd.log"); }; destination d_dnslogs { file("/u1/syslog/$HOST/$YEAR$MONTH$DAY/dnslogs.log"); }; destination d_logstash { tcp("127.0.0.1" port(5140) template("$R_ISODATE <$FACILITY_NUM.$LEVEL_NUM> $HOST $MSGHDR $MESSAGE\n") frac_digits(3) template-escape(no)); pipe("/var/log/logstash-pipe" template("$R_ISODATE <$FACILITY_NUM.$LEVEL_NUM> $HOST $MSGHDR $MESSAGE\n") frac_digits(3) template-escape(no)); }; destination d_userauth { tcp("abc.xyz.com" port(13456)); }; destination d_otto { tcp("abc.xyz.com" port(13456)); tcp("abc.xyz.com" port(13456)); }; destination d_notifier { tcp("abc.xyz.com" port(6000)); tcp("10.255.xx.yy" port(1248)); }; destination d_graylog { syslog("abc.xyz.com" transport("tcp") port(9514)); pipe("/var/log/graylog-pipe" ts-format(iso)); }; destination d_gtsadfeed { syslog("abc.xyz.com" transport("udp") port(514)); }; filter f_kernel { facility(kern); }; filter f_default { level(info..emerg) and not (facility(mail) or facility(authpriv) or facility(cron)) and not message("Syslog connection (accepted|closed)"); }; filter f_auth { facility(auth,authpriv); }; filter f_mail { facility(mail); }; filter f_emergency { level(emerg); }; filter f_news { facility(uucp) or (facility(news) and level(crit..emerg)); }; filter f_boot { facility(local7); }; filter f_cron { facility(cron,solaris-cron); }; filter f_user { facility(user); }; filter f_daemon { facility(daemon); }; filter f_lpr { facility(lpr); }; filter f_dnslogs { program("mydns_logger"); }; filter f_local0 { facility(local0); }; filter f_local1 { facility(local1) and not program("mydns_logger"); }; filter f_local2 { facility(local2); }; filter f_local3 { facility(local3); }; filter f_local4 { facility(local4); }; filter f_local5 { facility(local5) or tags("source_net"); }; # local5 is network, so is port 515 filter f_local6 { facility(local6); }; filter f_local7 { facility(local7); }; filter f_alert { level(alert); }; filter f_crit { level(crit); }; filter f_err { level(err); }; filter f_warn { level(warn); }; filter f_notice { level(notice); }; filter f_info { level(info); }; filter f_debug { level(debug); }; filter f_nonet { not facility(local4) and not facility(local5) and not tags("source_net"); }; filter f_nocf3 { not program("cf3"); }; filter f_nodhcpd { not program("dhcpd"); }; filter f_windows { tags("windows"); }; filter f_snmptrapd { program("snmptrapd"); }; filter f_userauth { not facility(local3); }; filter f_notifier_filter { not match("ASA-4-302015|ASA-4- 302013|TRAFFIC|permitted|Deny|Denied|denied", value("MESSAGE")); }; filter f_gtsadfeed_filter { host("*-adc*.abc.xyz.com" type(glob)); }; rewrite f_rewrite_name { set("$FULLHOST_FROM", value("HOST") condition(not tags("windows") and not match("REMOTELOG", value("MESSAGE")))); }; rewrite r_rewrite_name_windows { set("$FULLHOST_FROM", value("HOST") condition(not match("REMOTELOG", value("MESSAGE")))); }; rewrite r_snmptrapd { subst("^([^ ]+) (.*)", "${2}", value("MESSAGE")); set("${1}", value("HOST")); }; log { source(s_sys); filter(f_kernel); destination(d_kern); }; log { source(s_sys); filter(f_default); destination(d_mesg); }; log { source(s_sys); filter(f_auth); destination(d_auth); }; log { source(s_sys); filter(f_mail); destination(d_mail); }; log { source(s_sys); filter(f_emergency); destination(d_mlal); }; log { source(s_sys); filter(f_news); destination(d_spol); }; log { source(s_sys); filter(f_boot); destination(d_boot); }; log { source(s_sys); filter(f_cron); destination(d_cron); }; log { source(s_sys); filter(f_snmptrapd); rewrite(r_snmptrapd); destination(d_networkx); destination(d_logstash); log { filter(f_notifier_filter); destination(d_notifier); }; }; log { source(s_net); source(s_udp); source(s_tcp); source(s_sys); source(s_windows); log { filter(f_userauth); destination(d_userauth); destination(d_otto); }; log { rewrite(f_rewrite_name); log { destination(d_logstash); }; log { filter(f_nocf3); filter(f_nodhcpd); destination(d_graylog); }; log { filter(f_user); destination(d_userx); }; log { filter(f_kernel); destination(d_kernx); }; log { filter(f_mail); destination(d_mailx); }; log { filter(f_daemon); destination(d_daemonx); }; log { filter(f_auth); destination(d_authx); }; log { filter(f_lpr); destination(d_lprx); }; log { filter(f_cron); destination(d_cronx); }; log { filter(f_local0); destination(d_local0); }; log { filter(f_local1); destination(d_local1); }; log { filter(f_local2); destination(d_authx); }; log { filter(f_dnslogs); destination(d_dnslogs); }; log { filter(f_local4); destination(d_firewallx); log { filter(f_notifier_filter); destination(d_notifier); }; }; log { filter(f_local5); destination(d_networkx); log { filter(f_notifier_filter); destination(d_notifier); }; }; log { filter(f_local6); destination(d_local6); }; log { filter(f_local7); destination(d_mp); }; log { filter(f_windows); filter(f_gtsadfeed_filter); rewrite(r_rewrite_name_windows); destination(d_gtsadfeed); }; }; }; Could you please advise? Regards, Soumyadip

2 1

All surpassed messages are from Dec 31
by Scot Needy 22 Oct '16

22 Oct '16

This is strange. All suppressed messages I see have the Msg date re-written as "Dec 31 23:59:58”. Date never changes. Msg: Dec 31 23:59:58 192.168.100.73 Fdm[31436]: Last message '[FFE56B90 verbose 'P' repeated 1 times, suppressed by syslog-ng on

2 5

syslog-ng: list of changes
by Budai, László 21 Oct '16

21 Oct '16

Hi, today we merged some pull requests ( https://github.com/balabit/syslog-ng ). Changes: - Java destination updates - Support HDFS 2.7.3 - Support Elasticsearch 2.4 - release workflow - a new release branch created - debian package scripts are available only on that branch - Merged group unset <https://github.com/balabit/syslog-ng/pull/1235> feature - Fixed riemann configuration parse error <https://github.com/balabit/syslog-ng/issues/1212> - Fixed DNS cache list corruption <https://github.com/balabit/syslog-ng/pull/1218> regards, Laszlo Budai

1 0

AMQP Module not present?
by Thomas Polliard 20 Oct '16

20 Oct '16

The documentation seems to imply that the amqp driver should be available in the OSE version of syslog. I am running on a RHEL 7 systems with syslog-ng installed from EPEL. syslog-ng.x86_64 3.5.6-3.el7 @epel syslog-ng-devel.x86_64 3.5.6-3.el7 epel syslog-ng-geoip.x86_64 3.5.6-3.el7 epel syslog-ng-json.x86_64 3.5.6-3.el7 epel syslog-ng-libdbi.x86_64 3.5.6-3.el7 epel syslog-ng-mongodb.x86_64 3.5.6-3.el7 epel syslog-ng-redis.x86_64 3.5.6-3.el7 epel syslog-ng-smtp.x86_64 3.5.6-3.el7 epel When I try and load the amqp driver I get Error parsing destination, destination plugin amqp not found in /etc/syslog-ng/conf.d/51-ampq.conf at line 3, column 2: included from /etc/syslog-ng/syslog-ng.conf line 68, column 1 amqp( ^^^^ Any help would be appreciated. I am assuming I am either, missing a package that I should have installed or there is some missing information in the documentation. The document I was reading was https://www.balabit.com/documents/syslog-ng-ose-latest-guides/en/syslog-ng-… Thanks again -- *Thomas J. Polliard* -- -------------------------------------------------- This e-mail transmission contains information intended only for the use of the recipient(s) named above. Further, it contains information that may be privileged and confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message (including any attachments) is strictly prohibited. If you have received this e-mail in error, please notify the sender by reply e-mail and then delete this message from your mail system. Thank you for your compliance.

2 1

syslog-ng fails logging to existing sqlite database
by Andrea Laini 19 Oct '16

19 Oct '16

Hello everybody, I would like to ask you a question about libdbi (version 0.8.4.1 with libdbi-drivers 0.8.3). I'm using syslog-ng 3.5.4.1 on my Yocto Poky 1.7 Linux distro. I need to log my data into a sqlite3 database and everything works fine, but the database has not be written: no log data stored. According to debug infos, it seems that syslog-ng recognizes that the database exists, connects to it, found (with the sql statement "SELECT * FROM tableName WHERE 0=1) that the table named "tableName" exists but it gets an error when verifying columns' names; so it tries to add a column with that name to the table, but the operation fails since this column already exists. I've googled and search on the web, but I've found nothing interesting. Trying syslog-ng 3.6.4 doesn't change anything, while using libdbi 0.9.0 returns an error when compiling due to mismatch between function signature in the source and header file. Have you any suggestions? Thanks in advance, Regards Andrea Please be informed that our offices will be closed for National Holidays from Monday 31/10/16 to Tuesday 01/11/16 included. We will be back on Wednesday 02/11/16. Vi ricordiamo che saremo chiusi per festività i giorni lunedì 31/10/16 e martedì 01/11/16. Saremo nuovamente operativi da mercoledì 02/11/16. Andrea Laini Email: andrea.laini(a)claypaky.it<mailto:andrea.laini@claypaky.it> _________________________________ Clay Paky S.p.A. Via Pastrengo, 3/b - 24068 Seriate (BG) - ITALY Phone: +39 - 035.654.311 - Fax: +39 - 035.30.18.76 Web: www.claypaky.it<http://www.claypaky.it/> _________________________________ Read our Disclaimer @ www.claypaky.it/disclaimer<http://www.claypaky.it/disclaimer/index.html>

2 4