Topic: help cannot login root

[mgb]

login admin is ok
smb is ok
mail is not good
server-manager is not good
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, admin and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.
 log ftp://217.194.194.154/linux/messages.txt

[mmccarn]

I see a lot of this

Dec 19 09:56:04 mail PAM-securetty[2237]: /etc/securetty is either world writable or not a normal file

in your messages.txt.

From this link http://www.linuxquestions.org/questions/linux-security-4/securetty-and-login-45396/ it looks like you may want to:

Code: [Select]

chmod 600 /etc/securetty

Then re-try your login.

If that fixes it, then you need to figure out how /etc/securetty acquired insecure file permissions...

On my system, this file contains the following:

Code: [Select]

tty1
tty2
tty3
tty4
tty5
tty6
tty7
tty8


[cactus]

I hope this is your test server and not your production server as I see some dangerous instructions as well:

As I see in your log files you did update your system (due to the necessary events at Dec 16 around 16:25):

Code: [Select]

Dec 16 16:26:01 mail esmith::event[2614]: Processing event: bootstrap-console-save 
Dec 16 16:26:01 mail esmith::event[2614]: Running event handler: /etc/e-smith/events/bootstrap-console-save/S00initialize-default-databases
Dec 16 16:26:01 mail esmith::event[2614]: Migrating existing database networks 
Dec 16 16:26:01 mail esmith::event[2614]: Migrating existing database domains 
Dec 16 16:26:01 mail esmith::event[2614]: Migrating existing database yum_repositories 
Dec 16 16:26:01 mail esmith::event[2614]: Migrating existing database mailpatterns 
Dec 16 16:26:01 mail esmith::event[2614]: Migrating existing database yum_installed 
Dec 16 16:26:01 mail esmith::event[2614]: Migrating existing database spamassassin 
Dec 16 16:26:01 mail esmith::event[2614]: Migrating existing database configuration 
Dec 16 16:26:03 mail esmith::event[2614]: Migrating existing database hosts 
Dec 16 16:26:03 mail esmith::event[2614]: Migrating existing database yum_updates 
Dec 16 16:26:03 mail esmith::event[2614]: Migrating existing database yum_available 
Dec 16 16:26:03 mail esmith::event[2614]: Migrating existing database accounts 
Dec 16 16:26:03 mail esmith::event[2614]: Migrating existing database backups 
Dec 16 16:26:03 mail esmith::event[2614]: S00initialize-default-databases=action|Event|bootstrap-console-save|Action|S00initialize-default-databases|Start|1197815161 73900|End|1197815163 473780|Elapsed|2.39988
Dec 16 16:26:03 mail esmith::event[2614]: Running event handler: /etc/e-smith/events/bootstrap-console-save/S03conf-hostsdb
Dec 16 16:26:03 mail esmith::event[2614]: S03conf-hostsdb=action|Event|bootstrap-console-save|Action|S03conf-hostsdb|Start|1197815163 474053|End|1197815163 620552|Elapsed|0.146499
Dec 16 16:26:03 mail esmith::event[2614]: Running event handler: /etc/e-smith/events/bootstrap-console-save/S04purge-domain
Dec 16 16:26:03 mail esmith::event[2614]: S04purge-domain=action|Event|bootstrap-console-save|Action|S04purge-domain|Start|1197815163 620899|End|1197815163 750756|Elapsed|0.129857
Dec 16 16:26:03 mail esmith::event[2614]: Running event handler: /etc/e-smith/events/actions/generic_template_expand
... and see you disable the sme8os repository a few days later (Dec 19 around 09:26):

Code: [Select]

Dec 19 09:36:12 mail /etc/e-smith/web/panels/manager/cgi-bin/yum[4972]: /home/e-smith/db/yum_repositories: OLD sme8os=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/testing/8/smeos/i386/|EnableGroups|yes|GPGCheck|no|Name|SME Server 8 - smeos|Visible|yes|status|enabled
Dec 19 09:36:12 mail /etc/e-smith/web/panels/manager/cgi-bin/yum[4972]: /home/e-smith/db/yum_repositories: NEW sme8os=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/testing/8/smeos/i386/|EnableGroups|yes|GPGCheck|no|Name|SME Server 8 - smeos|Visible|yes|status|disabled
Dec 19 09:36:12 mail /etc/e-smith/web/panels/manager/cgi-bin/yum[4972]: /home/e-smith/db/yum_repositories: OLD smeupdates-testing=repository|BaseURL|http://mirror.contribs.org/pub/smeserver/releases/7/smeupdates-testing/$basearch|EnableGroups|yes|GPGCheck|yes|MirrorList|file:///etc/yum.repos.d/mirrors-smeupdates-testing|Name|SME Server - updates testing|Visible|yes|status|enabled
Dec 19 09:36:12 mail /etc/e-smith/web/panels/manager/cgi-bin/yum[4972]: /home/e-smith/db/yum_repositories: NEW smeupdates-testing=repository|BaseURL|http://mirror.contribs.org/pub/smeserver/releases/7/smeupdates-testing/$basearch|EnableGroups|yes|GPGCheck|yes|MirrorList|file:///etc/yum.repos.d/mirrors-smeupdates-testing|Name|SME Server - updates testing|Visible|yes|status|disabled
Dec 19 09:37:13 mail /etc/e-smith/web/panels/manager/cgi-bin/groups[5044]: /home/e-smith/db/accounts: OLD tot=group|Description|tot|Gid|5014|Members|admin|Uid|5014
Dec 19 09:37:13 mail /etc/e-smith/web/panels/manager/cgi-bin/groups[5044]: /home/e-smith/db/accounts: NEW tot=group-deleted|Description|tot|Gid|5014|Members|admin|Uid|5014
I suspect that you updated from the sme8os repository. Can you confirm that? Can you post the /var/log/yum.log from that update so we can see if you did leave the sme8os repository enabled and perhaps drag in any RPMS from there unintended?

[mgb]

Thank You
cannot login root 
to fixes
chmod 600 /etc/securetty

[mgb]

log yum http://217.194.194.155/log/
to fix login
1 - boot
start sme  sme ... 1

chmod 600 /etc/securetty
2 boot
login is ok
in server-manager is
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
 
Please contact the server administrator, admin and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

[cactus]

log yum http://217.194.194.155/log/

Unfortunately your link does not work...

[mgb]

log yum http://217.194.194.156/log/

? to backup  from root  to sme-server 7.2
backup smeserver.zip
for new server  7.3
(I hope this is your test server and not your production server as I see some dangerous instructions as well:
)

[cactus]

log yum http://217.194.194.156/log/

Are you sure this is the latest data as I am still missing the part of Dec 16th?

Waht did you do on your server at December 16th around 1630 local time?

[mgb]

 copy all log  to http


help  to backup  from root  to sme-server 7.2 smeserver.tgz
the backup from admin is not work
backup smeserver.tgz
i need all users profile
for new server  7.3 open   backup smeserver.tgz

[cactus]

copy all log  to http


help  to backup  from root  to sme-server 7.2 smeserver.tgz
the backup from admin is not work
backup smeserver.tgz
i need all users profile
for new server  7.3 open   backup smeserver.tgz

Please try and use the quote function to clarify your replies...

I am still not clear on how and from where you did retrieve the log files you have put on your web server. Did you take them from the server or from a backup?

You also did not specify what actions you performed on Dec 16th around 16.30 (local time).

[mgb]

 
http://217.194.194.156/log/new
the server is not work server-managrt  217.194.194.156


look link http://217.194.194.156/log/new/log/messages.20071115011202
check pass; user unknown !!! 15 06:34:05  is not mgb