[Xiaochun Tong]

What versions of Cloverleaf does Infor currently support?

[Xiaochun Tong]

Changing the /etc/password file to use the shell /bin/ksh instead of /bin/bash did the trick. Thanks!

[Xiaochun Tong]

We are upgrading from v6.0 to v6.2 and migrating from AIX to Linux. I have a tcl proc that used to work but no longer works in the new environment. The error:

[sms :sms :ERR /0:  f_muse_rslt:04/14/2018 11:20:58] Tcl error:

[sms :sms :ERR /0:  f_muse_rslt:–/–/—- –:–:–]    msgId   = message0

[sms :sms :ERR /0:  f_muse_rslt:–/–/—- –:–:–]    proc    = ‘UICformatMusepdf’

[sms :sms :ERR /0:  f_muse_rslt:–/–/—- –:–:–]    args    = ”

[sms :sms :ERR /0:  f_muse_rslt:–/–/—- –:–:–]    result  = ‘uudecode: /tmp/muse/04003286920180414112058.uu: No `begin’ line’

[sms :sms :ERR /0:  f_muse_rslt:–/–/—- –:–:–]    errorInfo: ‘

[sms :sms :ERR /0:  f_muse_rslt:–/–/—- –:–:–] uudecode: /tmp/muse/04003286920180414112058.uu: No `begin’ line

[sms :sms :ERR /0:  f_muse_rslt:–/–/—- –:–:–]     while executing

[sms :sms :ERR /0:  f_muse_rslt:–/–/—- –:–:–] “exec uudecode -o ${path}${pdf_file} ${path}${encoded_file}”

[sms :sms :ERR /0:  f_muse_rslt:–/–/—- –:–:–]     (procedure “UICformatMusepdf” line 121)

When I ran the uudecode command from the tcl prompt, it works just fine and created the pdf file. But when it runs from within the tcl proc, the error comes up.

[Xiaochun Tong]

Thanks for all your advice.

This is the response I got back from support:

We officially support current release and one back. So that is 6.0 and 5.8.x.x. We would continue official support of 5.8 until another major release comes out. We just released 6.0 a few months back and have net even released the first patch for that version. At the present time I have heard no discussions for plans for next release. So 5.8 should be supported for a while.

[Xiaochun Tong]

This is what I had to do to clear the errors:

monitor daemon cleanup. This is for cleaning up the moniotr daemon when pid file has been deleted or when the monitor daemon is locked up and not communicating.

These steps can be done while engines are running so just ignore the engines.

Run ps -ef | grep monitord or ps -ef | grep site name or ps -ef | grep monitord | grep sitename

This will allow you to see what process id the monitor daemon is running under.

You will need to do a kill -9 on the relevant process id number.

Remove the pid and cmd_port files if they exist in the exec/hcimonitord directory.

Run hcisitectl -sm to restart the monitor daemon or hcisitectl -s if both daemons are down and need starting.

[Xiaochun Tong]

I considere QDX upgrade as an important subject topic by itself as it is an on-going process for all of us who maintain the application.  It would be nice if you can create a seperate category just for upgrade.

[Author]

Replies