On Mon, 12 Nov 2007 23:12:21 +0100, Markus Schweitzer wrote: > Hi! > > I have upgraded my bacula on a server (Fedora Linux) from version > 1.38.11 to 2.2.5. I have made a "configure, make, make install" to the > location of my 1.38.11 as recommended in the manual. After that, I have > upgraded the database with the script. > > Problem: When I apply the parameter --version to the files (bconsole, > sd, fd, dir) in /sbin/ I get the version number 2.2.5. But when I start > the bconsole, then it prints "1000 OK: route66-dir Version: 1.38.11 (28 > June 2006)". > > Is this a normal behaviour? Did I have done the upgrade right?
Obviously not. Maybe the old binaries resides not in /sbin but in /usr/ sbin or somewhere else and the startup skripts were not updated and are still pointing to the old locations ? Maybe one of the following actions give new insights: Look in your startup skripts to find out if the correct binary is started. Do a Filesystem search to find out if multiple versions are installed. Examine the running daemons with lsof or similar. Stop the daemon und start manually (not through a startup skript) > > Markus. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Still grepping through > log files to find problems? Stop. Now Search log events and > configuration files using AJAX and a browser. Download your FREE copy of > Splunk now >> http://get.splunk.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
