[syslog-ng] syslog-ng upgrade

[Balazs Scheidler]

hi,

also, since this is pe related, the support guys should help, even if you have questions relating to the upgrade.

----- Original message -----
> Looks like the upgrade was successful. BTW 'rpm -U <file>' is the
> package upgrade method. When it comes to updating the configuration
> file (which isn't snd shouldn't be automated) then reading the message
> you quoted won't hurt.
> 
> On Wed, Aug 8, 2012 at 7:15 PM, James McDonald <jmcdonald at lce.com> wrote:
> > Does anyone know what needs to be done to successfully upgrade from
> > 4.1 to 4.2 (F2)?   I tried simply stopping the service and running ‘rpm
> > –ivh syslog-ng……rpm –force’ but it did not complete successfully.   I
> > added the –force command because it was complaining of file conflicts.
> >   Balabit has requested I upgrade to this version, as they try to help
> > me figure out my other problem I’m having with the syslog-ng service,
> > but I was unable to find any documentation or get a response from
> > Balabit yet.   I thought I would see if anyone here had performed the
> > upgrade and knew what needed to be done.   Here is the output I got
> > when I tried to run it:
> > 
> > 
> > 
> > rpm -ivh syslog-ng-premium-edition-4.2.3-1.rhel5.i386.r
> > pm --force
> > 
> > warning: syslog-ng-premium-edition-4.2.3-1.rhel5.i386.rpm: Header V4
> > DSA signature: NOKEY, key ID 2aa28252
> > 
> > Preparing...                               ###########################################
> > [100%]
> > 
> > *IMPORTANT NOTICE - NEW LICENSE REQUIRED FOR MULTI-CPU OPERATION*
> > 
> > 
> > 
> > Please note that the 4.2 version of syslog-ng Premium Edition includes
> > multi-threaded processing
> > 
> > with a 2 CPU core limit.   If you are upgrading your syslog-ng server
> > from version 4.1 to 4.2
> > 
> > and your syslog-ng deployment requires more than 2 CPU cores, you will
> > need to obtain a new
> > 
> > license file, free of charge, from the BalaBit sales department. Please
> > contact the sales
> > 
> > department at sales at balabit.com.
> > 
> > 
> > 
> > Shutting down kernel logger: [FAILED]
> > 
> > Shutting down system logger: [FAILED]
> > 
> > Stopping syslog-ng:       1:syslog-ng-premium-editiwarning:
> > /opt/syslog-ng/etc/syslog-ng.conf created as
> > /opt/syslog-ng/etc/syslog-ng.conf.rpmnew
> > 
> > ########################################### [100%]
> > 
> > Starting syslog-ng: WARNING: window sizing for network sources has
> > changed in syslog-ng 4.1. The window size is the value of the
> > log_iw_size() option divided by the value of max_connections(). If
> > log_iw_size()/max_connections() is lower than 100, it is automatically
> > increased to 100. Adjust the log_fifo_size() option if needed to avoid
> > message loss.; orig_window_size='1', new_window_size='100',
> > min_log_fifo_size='100000'
> > 
> > [   OK   ]
> > 
> > 
> > 
> > Thanks,
> > 
> > James McDonald
> > 
> > System Administrator
> > 
> > RHCSA, Security+
> > 
> > jmcdonald at lce.com
> > 
> > 
> > 
> > 
> > ______________________________________________________________________________
> > 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
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20120810/89a51892/attachment.htm