03-14-2005
Login Error 3004-304
I am trying to log on and get an error "3004-304 You are not allowed to login at this time.". This happens with both "root" and "admin" (the only other user ID on the system). System console or telnet session, doesn't matter. When I reboot the system, which I can only do with the power button since I can't sign on to issue shutdown, I can again log on, but after a day or two the problem returns. The system is obviously still running because I'm not having any problems with TSM backups. Google turns up nothing. Does anyone have any ideas?
Thanks,
Dino
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
we are using SCO Open Server 5.0.7 on HP ProLiant DL380 G4 Intel(R) Xeon(TM) CPU 2.8 dual processor. 2 GB MEM.
The error message is :
ps: RDUBLK: Cannot find process ID ....: No such device or address (error 6)
Best regards,
Abdullah Sekman (2 Replies)
Discussion started by: Abdullah Sekman
2 Replies
2. UNIX for Advanced & Expert Users
I encounters a VSIFAX related error:
vfxstat: Cannot login to server on rsac3: Connect error to host 172.16.1.45: Invalid argument
It started happening last night with a core dump. Then we can't start VSIFAX again.
I am runing VSI-FAX 4.2 on AIX box (0 Replies)
Discussion started by: b_jin
0 Replies
3. AIX
Guys
I have an AIX 5.3 box.I am getting following messages if i try to switch to any non root user.
bash-3.00# su - sys
3004-505 Cannot set process environment.
bash-3.00# su - daemon
3004-505 Cannot set process environment.
bash-3.00# su - adm
3004-505 Cannot set process environment.... (4 Replies)
Discussion started by: ak835
4 Replies
4. AIX
hello, I am trying to log on and get an error "3004-304 You are not allowed to login at this time.".
The server is in production level, works as a cluster under hacmp, the other server took the services but I cannot log into the first one.
Please help me because I need to solve the problem as... (2 Replies)
Discussion started by: andwhat
2 Replies
5. Solaris
Hello World ~
HW : SUN Fire V240
OS : Solaris 8
Error message prompts 'rmclomv ... SC login failure ...' on terminal.
and
Error Message prompts continually 'SC Login Failure for user Please login:' on Single Mode(init S)
The System is in normal operation, though
In case of rain, Can... (1 Reply)
Discussion started by: lifegeek
1 Replies
6. AIX
when all the users try to login using telnet they will counter the error 3004-031 . and they can not access the system . our application is sbglobus (temenos ) (6 Replies)
Discussion started by: thecobra151
6 Replies
7. AIX
Hello,
I have a strange situation here.
I am running an AIX6.1 machine and i face a problem when i am trying to login via telnet.
When i use my username and password to login to the server i get the following message:
3004-312 All available login sessions are in use.
The weird thing is that... (3 Replies)
Discussion started by: omonoiatis9
3 Replies
reboot(8) System Manager's Manual reboot(8)
NAME
reboot - Restarts the machine
SYNOPSIS
/usr/sbin/reboot [-dlnq]
DESCRIPTION
When the system is running and multiple users are logged in, use the shutdown -r command to perform a reboot operation. If no users are
logged in, use the reboot command.
The reboot command normally stops all running processes, syncs the disks, logs the reboot, and writes a shutdown entry in the login
accounting file, /var/adm/wtmp.
The reboot command uses the sync call to synchronize the disks, and to perform other shutdown activities such as resynchronizing the hard-
ware time-of-day clock. After these activities, the system reboots. By default, the system starts and the file systems are automatically
checked. If the start-up activities are successful, the system comes up in the default run-level.
You must have root privileges to use this command. Using the -n flag can result in file system damage.
FLAGS
Generates a crash dump of the system before halting it. Can be used with any of the other flags. Does not log the reboot using syslog
Does not sync the disks or log the reboot using syslog Performs a quick reboot without first shutting down running processes; does not log
the reboot using syslog
EXAMPLES
To enable the default reboot action, enter: reboot This command causes the system to stop all running processes, sync the disks, log the
shutdown, and perform other routine shutdown and reboot activities. To shut down the system without logging the reboot, enter: reboot -l
This command shuts down the system and performs all shutdown and reboot activities, except logging the shutdown. To reboot the system
abruptly, enter: reboot -q This command reboots the system abruptly without shutting down running processes.
FILES
Specifies the command path Specifies the login accounting file Specifies the path of the syslog daemon
RELATED INFORMATION
Commands: fsck(8), halt(8), init(8), savecore(8) shutdown(8), syslogd(8)
Functions: reboot(2), sync(2), syslog(3) delim off
reboot(8)