I'm making some progress I think in my tests to get OTRS 2.3.2 going, right now I'm testing how I'll get my DB moved forward. The instructions for UPGRADING the database from 2.2 to 2.3 say to "Run the migration script (as OTRS user, _not_ as root)" however I can't get "su otrs" to work, I remain logged in as myself. And if I try to ssh in as otrs in a new shell the connection is immediately closed. Can anyone suggest what I need to do? Thank you. -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com
Making a guess here, but sound right... It is probable that the otrs user is probably set to not allow logins. This is fairly easy to check for most linux flavors a "grep otrs /etc/passwd" should give you the answer. Usually the shell will be a directory/file that doesn't exist and often this is something like nologin or badsh (BAD SHell). If this is the case then the problem is just that... Read the passwd file for your account and change the directory to what your account says and you should be able to log. This assumes that you know the password for the otrs account. If not it's probably best to start from root and then su otrs. For security, when you are done with the upgrade change the otrs shell back to the 'nologin' shell. LQ
-----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Wes Plate Sent: Monday, October 06, 2008 8:43 PM To: OTRS Subject: [otrs] Run migration script as OTRS user, can't su otrs
I'm making some progress I think in my tests to get OTRS 2.3.2 going, right now I'm testing how I'll get my DB moved forward.
The instructions for UPGRADING the database from 2.2 to 2.3 say to "Run the migration script (as OTRS user, _not_ as root)" however I can't get "su otrs" to work, I remain logged in as myself. And if I try to ssh in as otrs in a new shell the connection is immediately closed.
Can anyone suggest what I need to do?
Thank you.
On 10/6/08 7:21 PM, "LQ Marshall" wrote:
It is probable that the otrs user is probably set to not allow logins. This is fairly easy to check for most linux flavors a "grep otrs /etc/passwd" should give you the answer. Usually the shell will be a directory/file that doesn't exist and often this is something like nologin or badsh (BAD SHell).
This got me to the answer. Thanks! I used Webmin to mess with the otrs user's settings and was able to get the script run. The test mostly worked! I'm looking at my old database in 2.3.2 now! Amazing. Now to figure out why I can't see my FAQ articles in the AgentFAQ view. -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com
LQ Marshall wrote:
It is probable that the otrs user is probably set to not allow logins. This is fairly easy to check for most linux flavors a "grep otrs /etc/ passwd" should give you the answer. Usually the shell will be a directory/ file that doesn't exist and often this is something like nologin or badsh (BAD SHell).
If this is the case then the problem is just that... Read the passwd file for your account and change the directory to what your account says and you should be able to log.
This assumes that you know the password for the otrs account. If not it's probably best to start from root and then su otrs.
For security, when you are done with the upgrade change the otrs shell back to the 'nologin' shell.
You can use the -s switch to su to specify a (one time) shell. No need to modify any files: # su -s /bin/bash - <user-that-normally-cannot-login> Nils Breunese.
participants (3)
-
LQ Marshall -
Nils Breunese (Lemonbit) -
Wes Plate