Upgrade problem 3.6 to 4.2

This is for the remaining stuff.

Moderator: sepma

Post Reply
ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Upgrade problem 3.6 to 4.2

Post by ian » June 6th, 2013, 2:51 am

I'm trying to update our SESAM 3.6 server to the latest release, running on SLES11.2 i386.
I've run rpm -Uvh sesam_srv-4.2.1-41.sles11.i586.rpm and get the following output:
Preparing... ########################################### [100%]
Check old Sesam version
Check update license
Check Sesam DB
Export Sesam DB
1:sesam_srv ########################################### [100%]
Correct Java VM >= 1.6 link already exists in 'sesam' directory.
Starting sesam:
Found new sesam version. Starting update ...
failed

STATUS=SUCCESS MSG=ok
Here's the contents of /var/opt/sesam/var/log/lgc/sm_startup.lcg file - it seems to fail when it tries to find the status of sm_main. Any idea what the problem may be?
9:18:09# Logging enabled for module SM_STARTUP: Loglevel 1, PID=2984, parent process: /opt/sesam/bin/sesam/sm_qm_main (PPID=2839)
9:18:09# +++ SM_STARTUP: $Id: sm_startup.c,v 1.99 2009/03/25 17:13:16 miraculix Exp $
9:18:09# *** READ_INI
9:18:09# INFO: prot-dir is existing
9:18:09# INFO: log/lgc-dir is existing
9:18:09# INI GLBV > gv_rw_prot_media = /var/opt/sesam/var/prot/media
9:18:09# Testing> /var/opt/sesam/var/prot/media Info: Directory is existing
9:18:09# INI GLBV > gv_rw_sel = /var/opt/sesam/var/sel
9:18:09# Testing> /var/opt/sesam/var/sel Info: Directory is existing
9:18:09# INI GLBV > gv_rw_prot = /var/opt/sesam/var/prot
9:18:09# Testing> /var/opt/sesam/var/prot Info: Directory is existing
9:18:09# INI GLBV > gv_rw_prepost = /var/opt/sesam/var/prepost
9:18:09# Testing> /var/opt/sesam/var/prepost Info: Directory is existing
9:18:09# INI GLBV > gv_rw_not = /var/opt/sesam/var/not
9:18:09# Testing> /var/opt/sesam/var/not Info: Directory is existing
9:18:09# INI GLBV > gv_rw_lis = /var/opt/sesam/var/lis
9:18:09# Testing> /var/opt/sesam/var/lis Info: Directory is existing
9:18:09# INI GLBV > gv_rw_info = /var/opt/sesam/var/work/info
9:18:09# Testing> /var/opt/sesam/var/work/info Info: Directory is existing
9:18:09# INI GLBV > gv_rw_db = /var/opt/sesam/var/db
9:18:09# Testing> /var/opt/sesam/var/db Info: Directory is existing
9:18:09# INI GLBV > gv_ro_gui = /opt/sesam/bin/gui
9:18:09# Testing> /opt/sesam/bin/gui Info: Directory is existing
9:18:09# INI GLBV > gv_ro_db = /opt/sesam/bin/db
9:18:09# Testing> /opt/sesam/bin/db Info: Directory is existing
9:18:09# INI GLBV > gv_rw_stpd = /var/opt/sesam/var/log/sms
9:18:09# Testing> /var/opt/sesam/var/log/sms Info: Directory is existing
9:18:09# INI GLBV > gv_rw_smslis = /var/opt/sesam/var/work/smslis
9:18:09# Testing> /var/opt/sesam/var/work/smslis Info: Directory is existing
9:18:09# INI GLBV > gv_rw_sms = /var/opt/sesam/var/work/smslis
9:18:09# Testing> /var/opt/sesam/var/work/smslis Info: Directory is existing
9:18:09# INI GLBV > gv_ro_stpd = /opt/sesam/bin/sms
9:18:09# Testing> /opt/sesam/bin/sms Info: Directory is existing
9:18:09# INI GLBV > gv_ro_sms = /opt/sesam/bin/sms
9:18:09# Testing> /opt/sesam/bin/sms Info: Directory is existing
9:18:09# INI GLBV > gv_rw_glbv = /var/opt/sesam/var/glbv
9:18:09# Testing> /var/opt/sesam/var/glbv Info: Directory is existing
9:18:09# INI GLBV > gv_rw_qm = /var/opt/sesam/var/qm
9:18:09# Testing> /var/opt/sesam/var/qm Info: Directory is existing
9:18:09# INI GLBV > gv_rw_sbc_times = /var/opt/sesam/var/times
9:18:09# Testing> /var/opt/sesam/var/times Info: Directory is existing
9:18:09# INI GLBV > gv_rw_times = /var/opt/sesam/var/times
9:18:09# Testing> /var/opt/sesam/var/times Info: Directory is existing
9:18:09# INI GLBV > gv_rw_sbc_log = /var/opt/sesam/var/log/sbc
9:18:09# Testing> /var/opt/sesam/var/log/sbc Info: Directory is existing
9:18:09# INI GLBV > gv_rw_sbc = /var/opt/sesam/var/log/sbc
9:18:09# Testing> /var/opt/sesam/var/log/sbc Info: Directory is existing
9:18:09# INI GLBV > gv_rw_lgc = /var/opt/sesam/var/log/lgc
9:18:09# Testing> /var/opt/sesam/var/log/lgc Info: Directory is existing
9:18:09# INI GLBV > gv_rw_tmp = /var/opt/sesam/var/tmp
9:18:09# Testing> /var/opt/sesam/var/tmp Info: Directory is existing
9:18:09# INI GLBV > gv_rw_work = /var/opt/sesam/var/work
9:18:09# Testing> /var/opt/sesam/var/work Info: Directory is existing
9:18:09# INI GLBV > gv_rw_ini = /var/opt/sesam/var/ini
9:18:09# Testing> /var/opt/sesam/var/ini Info: Directory is existing
9:18:09# INI GLBV > gv_ro_bin = /opt/sesam/bin/sesam
9:18:09# Testing> /opt/sesam/bin/sesam Info: Directory is existing
9:18:09# INI GLBV > gv_rw = /var/opt/sesam
9:18:09# Testing> /var/opt/sesam Info: Directory is existing
9:18:09# INI GLBV > gv_ro = /opt/sesam
9:18:09# Testing> /opt/sesam Info: Directory is existing
9:18:09# --- READ_INI success
9:18:09# +++ i_CREATE_DIR_LOCAL
9:18:09# --- i_CREATE_DIR_LOCAL returns 1 msg= /var/opt/sesam/var/log/lgc/ already existing
9:18:09# gv_prot= /var/opt/sesam/var/prot/20130606.prt
9:18:09# *** Check if sm_main is already running
9:18:14# sm_main status returned 0: sm_main status
9:18:14# sm_main is already running so we go on with startup
9:18:14# +++ DB_ACCESS id=NULL SQL=update results set state='c',msg='Canceled by Sesam startup.' where state='a' or state='q'
9:18:14# --- DB_ACCESS returns 1 msg=ok
9:18:14# First DB statement done with retry 0, iSts 1
9:18:14# +++ DB_ACCESS id=NULL SQL=update restore_results set state='c',msg='Canceled by Sesam startup.' where state='a' or state='q'
9:18:14# --- DB_ACCESS returns 1 msg=ok
9:18:14# +++ DB_ACCESS id=NULL SQL=update media_results set state='c',message='Canceled by Sesam startup.' where state='a' or state='q'
9:18:14# --- DB_ACCESS returns 1 msg=ok
9:18:14# +++ DB_ACCESS id=NULL SQL=update migration_results set state='c',msg='Canceled by Sesam startup.' where state='a' or state='q'
9:18:14# --- DB_ACCESS returns 1 msg=ok
9:18:14# +++ DB_ACCESS id=NULL SQL=update cal_sheets set state='c',msg='Canceled by Sesam startup.' where state='a' or state='q'
9:18:14# --- DB_ACCESS returns 1 msg=ok
9:18:14# +++ DB_ACCESS id=NULL SQL=update media set init_flag='n' where init_flag='y'
9:18:14# --- DB_ACCESS returns 1 msg=ok
9:18:14# *** create queue qu_all
9:18:14# +++ DB_SEL_GETVALUE
9:18:14# +++ DB_ACCESS id= SQL=select value from defaults where key='qu_all_joblimit' and user_name='sesam'
9:18:14# --- DB_ACCESS returns 1 msg=0
9:18:14# Error during DBaccess or no record found
9:18:14# --- DB_SEL_GETVALUE
9:18:14# +++ KRL QUE_INIT in $Id: sm_lib.c,v 1.673.2.3 2009/11/05 12:47:40 miraculix Exp $ qu_all 20
9:18:14# cmd = sm_qm init qu_all 20
9:18:14# STATUS=SUCCESS MSG=Job limit for resource queues changed to 20

9:18:14# --- KRL QUE_INIT returns 1 msg: Job limit for resource queues changed to 20

9:18:14# *** Auto configure devices started /opt/sesam/bin/sesam/sm_auto_conf_hw 0
9:18:21# *** Configuring drives
9:18:21# start_exe: sm_config_drives
9:18:21# +++ CMDLINE_PARSER: got command line: sm_config_drives
9:18:21# --- CMDLINE_PARSER: returns 0 arguments
9:18:21# PID of child: 3492
9:18:24# start_exe returns 0
9:18:24# *** Configuring loaders
9:18:24# start_exe: sm_config_loaders
9:18:24# +++ CMDLINE_PARSER: got command line: sm_config_loaders
9:18:24# --- CMDLINE_PARSER: returns 0 arguments
9:18:24# PID of child: 3573
9:18:25# start_exe returns 0
9:18:25# *** Preparing INFO system
9:18:25# +++ FILE_DELETE gv_rw_work:info.dat -> /var/opt/sesam/var/work/info.dat
9:18:25# remove(/var/opt/sesam/var/work/info.dat) failed try rmdir() for empty directory
9:18:25# --- FILE_DELETE returns 0
9:18:25# +++ FILE_DELETE gv_rw_work:info.tmp -> /var/opt/sesam/var/work/info.tmp
9:18:25# remove(/var/opt/sesam/var/work/info.tmp) failed try rmdir() for empty directory
9:18:25# --- FILE_DELETE returns 0
9:18:25# *** Looping all drives
9:18:25# +++ DB_ACCESS id=STARTUP SQL=select drive_num,device,loader_num from hw_drives
9:18:25# --- DB_ACCESS returns 1 msg=2
9:18:25# Drive 1 disk1 0
9:18:26# Drive 2 /dev/nst0 1
9:18:26# --- SM_STARTUP
9:18:26# +++ FINISH 0 Startup completed successfully
9:18:26# +++ DB_ACCESS id=NULL SQL=insert into results (task,datum,cnt,saveset,start_tim,stop_tim,fdi_typ,blocks,state,msg) values ('sm_startup','2013-06-06 00:00:00',1,'20130606091826','2013-06-06 09:18:09','2013-06-06 09:18:26','S',0,'0','Startup completed successfully')
9:18:27# --- DB_ACCESS returns 1 msg=ok
9:18:27# +++ DB_ACCESS id=NULL SQL=insert into cal_sheets (id,start,end_time,ev_type,state,priority,object,suppress,schedule,msg) values ('SU20130606091826','2013-06-06 09:18:09','2013-06-06 09:18:26','S','0','0','sm_startup','0','system start up','Startup completed successfully')
9:18:27# --- DB_ACCESS returns 1 msg=ok
9:18:27# --- FINISH SUCCESS Startup completed successfully
2013-06-06 9:29:46: Logging enabled for module SM_STARTUP: Loglevel 1, PID=4816, parent process: /bin/sh /etc/init.d/sesam start (PPID=4668)
2013-06-06 9:29:46: Build host: "Linux buildfix 2.6.16.60-0.21-bigsmp 1 SMP Tue May 6 12:41:02 UTC 2008 i686 i686 i386 GNU/Linux, GNU C Library stable release version 2.4 20080421"
2013-06-06 9:29:46: +++ SM_STARTUP: $Id: sm_startup.c,v 1.121 2013/01/25 14:11:50 kha Exp $
2013-06-06 9:29:46: *** READ_INI for Server
2013-06-06 9:29:46: INI GLBV > gv_rw_prot_media = /var/opt/sesam/var/prot/media
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/prot/media Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_sel = /var/opt/sesam/var/sel
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/sel Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_prot = /var/opt/sesam/var/prot
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/prot Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_prepost = /var/opt/sesam/var/prepost
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/prepost Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_not = /var/opt/sesam/var/not
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/not Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_lis = /var/opt/sesam/var/lis
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/lis Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_info = /var/opt/sesam/var/work/info
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/work/info Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_db = /var/opt/sesam/var/db
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/db Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_ro_gui = /opt/sesam/bin/gui
2013-06-06 9:29:46: Testing> /opt/sesam/bin/gui Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_ro_db = /opt/sesam/bin/db
2013-06-06 9:29:46: Testing> /opt/sesam/bin/db Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_stpd = /var/opt/sesam/var/log/sms
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/log/sms Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_smslis = /var/opt/sesam/var/work/smslis
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/work/smslis Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_sms = /var/opt/sesam/var/work/smslis
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/work/smslis Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_ro_stpd = /opt/sesam/bin/sms
2013-06-06 9:29:46: Testing> /opt/sesam/bin/sms Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_ro_sms = /opt/sesam/bin/sms
2013-06-06 9:29:46: Testing> /opt/sesam/bin/sms Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_glbv = /var/opt/sesam/var/glbv
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/glbv Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_qm = /var/opt/sesam/var/qm
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/qm Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_sbc_times = /var/opt/sesam/var/times
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/times Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_times = /var/opt/sesam/var/times
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/times Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_sbc_log = /var/opt/sesam/var/log/sbc
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/log/sbc Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_sbc = /var/opt/sesam/var/log/sbc
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/log/sbc Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_lgc = /var/opt/sesam/var/log/lgc
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/log/lgc Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_tmp = /var/opt/sesam/var/tmp
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/tmp Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_work = /var/opt/sesam/var/work
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/work Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw_ini = /var/opt/sesam/var/ini
2013-06-06 9:29:46: Testing> /var/opt/sesam/var/ini Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_ro_bin = /opt/sesam/bin/sesam
2013-06-06 9:29:46: Testing> /opt/sesam/bin/sesam Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_rw = /var/opt/sesam
2013-06-06 9:29:46: Testing> /var/opt/sesam Info: Directory is existing
2013-06-06 9:29:46: INI GLBV > gv_ro = /opt/sesam
2013-06-06 9:29:46: Testing> /opt/sesam Info: Directory is existing
2013-06-06 9:29:46: check gv_rw [/var/opt/sesam/] is parent of gv_rw_lis [/var/opt/sesam/var/lis/]
2013-06-06 9:29:46: --- READ_INI success
2013-06-06 9:29:46: +++ i_CREATE_DIR_LOCAL: /var/opt/sesam/var/log/lgc/
2013-06-06 9:29:46: --- i_CREATE_DIR_LOCAL returns 1 msg= /var/opt/sesam/var/log/lgc already existing
2013-06-06 9:29:46: gv_prot= /var/opt/sesam/var/prot/20130606.prt
2013-06-06 9:29:46: *** Check if sm_main is already running
2013-06-06 9:29:48: sm_main status returned 1: sm_main status
2013-06-06 9:29:50: sm_main status returned 1: sm_main status
2013-06-06 9:29:52: sm_main status returned 1: sm_main status
2013-06-06 9:29:54: sm_main status returned 1: sm_main status
2013-06-06 9:29:56: sm_main status returned 1: sm_main status
2013-06-06 9:29:58: sm_main status returned 1: sm_main status
2013-06-06 9:30:00: sm_main status returned 1: sm_main status
2013-06-06 9:30:02: sm_main status returned 1: sm_main status
2013-06-06 9:30:04: sm_main status returned 1: sm_main status
2013-06-06 9:30:06: sm_main status returned 1: sm_main status
2013-06-06 9:30:08: sm_main status returned 1: sm_main status
2013-06-06 9:30:10: sm_main status returned 1: sm_main status
2013-06-06 9:30:12: sm_main status returned 1: sm_main status
2013-06-06 9:30:14: sm_main status returned 1: sm_main status
2013-06-06 9:30:16: sm_main status returned 1: sm_main status
2013-06-06 9:30:19: sm_main status returned 1: sm_main status
2013-06-06 9:30:21: sm_main status returned 1: sm_main status
2013-06-06 9:30:23: sm_main status returned 1: sm_main status
2013-06-06 9:30:25: sm_main status returned 1: sm_main status
2013-06-06 9:30:27: sm_main status returned 1: sm_main status
2013-06-06 9:30:29: sm_main status returned 1: sm_main status
2013-06-06 9:30:29: ERROR: sm_main status returned 1
2013-06-06 9:30:29: --- SM_STARTUP: sm_main state is invalid >> exit with FATAL
2013-06-06 9:30:29: +++ i_NOTIFICATION: command [sm_alarm], module [SM_STARTUP], msg [Startup failed]
2013-06-06 9:30:29: +++ NOTIFY: command [sm_alarm], module [SM_STARTUP], msg [Startup failed]
2013-06-06 9:30:29: +++ CREATE_UNIQUE_ID: notification: Type: S Sema: notification
2013-06-06 9:30:29: --- CREATE_UNIQUE_ID: Id: 20130606093029303
2013-06-06 9:30:29: Temporary OutFile: [/var/opt/sesam/var/tmp/sm_alarm-20130606093029303.prt]
2013-06-06 9:30:29: There is no script sm_alarm at server
2013-06-06 9:30:29: --- NOTIFY: return status -3, msg [Startup failed]
2013-06-06 9:30:29: --- i_NOTIFICATION Status=-3 Msg=Startup failed
2013-06-06 9:30:29: +++ i_NOTIFICATION: command [sm_notify], module [SM_STARTUP], msg [Startup failed]
2013-06-06 9:30:29: +++ NOTIFY: command [sm_notify], module [SM_STARTUP], msg [Startup failed]
2013-06-06 9:30:29: +++ CREATE_UNIQUE_ID: notification: Type: S Sema: notification
2013-06-06 9:30:29: --- CREATE_UNIQUE_ID: Id: 20130606093029306
2013-06-06 9:30:29: Temporary OutFile: [/var/opt/sesam/var/tmp/sm_notify-20130606093029306.prt]
2013-06-06 9:30:29: +++ RCMD: backup, [sm_notify SM_STARTUP "Startup failed" ""], bAvoidProt 0, bAvoidErrProt 1
2013-06-06 9:30:29: Call for local server backup >> call i_PIPE_OPEN_RCMD()
2013-06-06 9:30:29: Set interpreter for command script
2013-06-06 9:30:29: --- RCMD: Exit [0], status [unknown], msg []
2013-06-06 9:30:29: RCMD Exit status = 0, msg []
2013-06-06 9:30:29: +++ FILE_DELETE /var/opt/sesam/var/tmp/sm_notify-20130606093029306.prt :== /var/opt/sesam/var/tmp/sm_notify-20130606093029306.prt
2013-06-06 9:30:29: --- FILE_DELETE returns 1
2013-06-06 9:30:29: --- NOTIFY: return status 0, msg [Startup failed]
2013-06-06 9:30:29: --- i_NOTIFICATION Status=0 Msg=Startup failed
2013-06-06 9:30:29: +++ DB_ACCESS id=NULL SQL=insert into results (task,sesam_date,cnt,saveset,start_time,stop_time,fdi_type,blocks,state,msg,uuid) values ('sm_startup','2013-06-06 00:00:00',1,'20130606093029','2013-06-06 09:29:46','2013-06-06 09:30:29','S',0,'X','Startup failed','1953facc-ce3c-11e2-934b-000c7620a467')
2013-06-06 9:30:29: sqlite3_get_table() returned SQLITE_ERROR
2013-06-06 9:30:29: --- DB_ACCESS returns 0 msg=table results has no column named sesam_date
2013-06-06 9:30:29: +++ KRL TRAP_DB_ERR in $Id: sm_lib.c,v 1.1025 2013/02/27 13:42:44 sesam Exp $ SM_STARTUP insert into results table results has no column named sesam_date
2013-06-06 9:30:29: --- KRL TRAP_DB_ERR exits with 1
Cheers,
Ian

jgb
Posts: 55
Joined: June 27th, 2011, 11:11 am
Spam Stop: No
SEP sesam: Software

Re: Upgrade problem 3.6 to 4.2

Post by jgb » June 6th, 2013, 8:44 am

Hi Ian,

it seems, that the upgrade has finished, but the sesam services can't start.

Please check (in a root shell with sesam profile set):

- any parts of sesam running ? ( ps ax | grep sm_ and ps ax | grep sesam )
- if yes, stop all processes (rcsesam stop or sm_main stop) ; check again
- try to start the parts of sesam step by step

sm_main start qm
sm_main start sepuler
sm_main start db
sm_main start rmi
sm_main start stpd
sm_main start sms
sm_main start passd
sm_main start ctrl

May be, one of the starts will fail. Then look in the <sesam_inst>/var/log/lgc/ folder for the latest changed log files ( ls -latr ). Inside these logs you can find the real cause for the problem. If possible, you can solve the problem by yourselve, if not, open a ticket at SEP support ( E-Mail to support@sep.de ).

JGB

ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Re: Upgrade problem 3.6 to 4.2

Post by ian » June 11th, 2013, 3:14 am

Thanks for the tip! There were no sesam processes running, so I tried sm_main start qm and got the following output:

2013-06-11 09:58:53: sm_main[5654] started
2013-06-11 09:58:53: Arguments: /opt/sesam/bin/sesam/sm_main start qm
Traceback (most recent call last):
File "/usr/local/lib/python2.6/site-packages/cx_Freeze/initscripts/Console.py", line 27, in <module>
File "sm_main.py", line 223, in <module>
File "sm_main.py", line 133, in read_sds_config
OSError: [Errno 2] No such file or directory: '/var/opt/sesam/var/ini//stpd_conf'

There was nothing useful in the log files, only:
2013-06-11 09:40:34: sm_main[5359] started
2013-06-11 09:40:34: Arguments: /opt/sesam/bin/sesam/sm_main start qm

So I tried creating a file called /var/opt/sesam/var/ini/stpd_conf, then tried starting qm again and it complained about a regular files with that name existing instead of a directory. So I deleted the file and created a stpd_conf directory and then SESAM started up and it all seems to be working!

I guess the installer didn't create the folder, maybe the double // indicates something missing in the path?

jgb
Posts: 55
Joined: June 27th, 2011, 11:11 am
Spam Stop: No
SEP sesam: Software

Re: Upgrade problem 3.6 to 4.2

Post by jgb » June 12th, 2013, 4:13 pm

Hi Ian,

please look in the folder /var/opt/sesam/var/log/lgc for files with the name

sm_db_update_<date of update>.*
sm_db_update_update_<date of update>.*

In the second log search for mkdir or stpd_conf . In this log file you can see what was going wrong (why the folder was not created).

Please post this part of the logfile.

JGB

ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Re: Upgrade problem 3.6 to 4.2

Post by ian » June 13th, 2013, 5:48 am

Here are the log files - the upgrade apparently thought the directory already existed!

sm_db_update_20130611.lgx:
2013-06-11 10:36:58: Logging enabled for module SM_DB_UPDATE: Loglevel 1, PID=6463, parent process: /bin/sh /opt/sesam/bin/sesam//sm_check_version (PPID=6226)
2013-06-11 10:36:58: Build host: "Linux sles1132fix 2.6.27.19-5-pae 1 SMP 2009-02-28 04:40:21 +0100 i686 i686 i386 GNU/Linux, GNU C Library stable release version 2.9 20081117"
2013-06-11 10:36:58: +++ ARGUMENTS
2013-06-11 10:36:58: INPUT: service 0, OldVersion 3.6.4.17, NewVersion 4.2.1.41, DBImportFile , IniFlg
sm_db_update_update_20130611.lgx:
2013-06-11 10:37:04: i_GetPrivateProfileString ( /opt/sesam/skel/sm_db_update.ini, [update 4.0.], step_13, szTmp )
2013-06-11 10:37:04: +++ PARSER cmd mkdir gv_rw_ini:stpd_conf (13)
2013-06-11 10:37:04: chdir(/var/opt/sesam/var/ini/stpd_conf) returned 0; Directory ["/var/opt/sesam/var/ini/stpd_conf"] already exists, skipping 'mkdir "/var/opt/sesam/var/ini/stpd_conf"'
2013-06-11 10:37:04: mkdir gv_rw_ini:stpd_conf returned 0
2013-06-11 10:37:04: --- PARSER

jgb
Posts: 55
Joined: June 27th, 2011, 11:11 am
Spam Stop: No
SEP sesam: Software

Re: Upgrade problem 3.6 to 4.2

Post by jgb » June 13th, 2013, 7:46 am

Hi Ian,

you have posted the log from 2013-06-11 . At this time the stpd_conf folder already exist.
Your first post was from 2013-06-06. I think in this log (your first upgrade attempt) you will see the real cause. May be, the logfile is already purged,

JGB

ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Re: Upgrade problem 3.6 to 4.2

Post by ian » June 14th, 2013, 12:09 am

Sorry, I should explain the sequence of events better:
On the 6th, I took a snapshot of the server, did the upgrade and made my first post.
Because SESAM wouldn't start, I then restored the snapshot so I had a working 3.6 system again.

Then on the 11th, I did the upgrade again from scratch, which was when I figured out the folder was missing. So the logs from the 11th are the correct ones - but I can't explain why the folder existed at that point, but not when SESAm tried to start after the upgrade!

I am having one issue with with the upgraded system and our OES2 server timing out which has never happened before, will post something in the backups forum about that as I don't think it's related to this issue.

jgb
Posts: 55
Joined: June 27th, 2011, 11:11 am
Spam Stop: No
SEP sesam: Software

Re: Upgrade problem 3.6 to 4.2

Post by jgb » June 14th, 2013, 10:40 am

Hi Ian,

I've no idea who or what delete the stpd_conf folder. You can grep the sesam logs for the delete event and also any other logs in /var/log .

Best regards

JGB

Post Reply