I'm trying to su to a user on a CentOS 6.4 x86_64 box and get the
error in the subject:
[user1@cent6.4box ~]$ sudo su - user2
su: cannot set user id: Resource temporarily unavailable
[user1@cent6.4box ~]$
The limits.conf file has the following entries:
* so
Check shared memory and semaphores. Its probable that some other
application is swallowing the resource sudo needs. This is a common
method of DOS attacks and 'bot nets.
--Bruce
On Mon, 2014-03-10 at 10:05 -0400, Brian Chabot wrote:
> I'm trying to su to a user on a CentOS 6.4 x86_64 box and get
Might be semaphores?
On 3/10/2014 10:05 AM, Brian Chabot wrote:
> I'm trying to su to a user on a CentOS 6.4 x86_64 box and get the
> error in the subject:
>
> [user1@cent6.4box ~]$ sudo su - user2
> su: cannot set user id: Resource temporarily unavailable
> [user1@cent6.4box ~]$
>
> The limits.co
[user1@cent6.4box ~]$ ipcs -m
-- Shared Memory Segments
keyshmid owner perms bytes nattch status
0x6c000803 98304 zabbix 600995952 5
[user1@cent6.4box ~]$ ipcs -s
-- Semaphore Arrays
keysemid owner p
Also, disk space and RAM are aplenty...
Is there any way to tell *which* resource is unavailable?
Brian Chabot
On Mon, Mar 10, 2014 at 10:19 AM, Brian Chabot wrote:
> [user1@cent6.4box ~]$ ipcs -m
>
> -- Shared Memory Segments
> keyshmid owner perms bytes
On 2014-03-10 10:05, Brian Chabot wrote:
> I'm trying to su to a user on a CentOS 6.4 x86_64 box and get the
> error in the subject:
>
> [user1@cent6.4box ~]$ sudo su - user2
> su: cannot set user id: Resource temporarily unavailable
> [user1@cent6.4box ~]$
This is where, when desperate, I whip
On 3/10/2014 10:20 AM, Brian Chabot wrote:
> Also, disk space and RAM are aplenty...
>
> Is there any way to tell *which* resource is unavailable?
> Brian Chabot
>
Two other thoughts:
- Is SELinux enabled? Check the logs and see if there's anything
strange there.
- try using strace to see whic
THANK YOU!
I found the error.
Thanks to Ken for the strace idea, I looked through the resultant log
and found this line:
9519 read(8, "# Default limit for number of user's processes to
prevent\n# accidental fork bombs.\n# See rhbz #432903 for
reasoning.\n\n* softnproc 1024\nroo
Another vote for strace. Depending on circumstances I
sometimes first startup a separate session thus:
script /tmp/tediousDebugSession.log
...and then just allow the strace+program command to let
fly via stdout. It can be a mess but having program output
intermixed with the resultant strac
I'm a generalist looking for work (SysEng/SysAdmin/other?)
within reasonable commuting distance from Chelmsford, MA.
Please email me if you have any leads or want further info...
Thanks,
--Michael O'Donnell
___
gnhlug-discuss mailing list
gnhlug-di
Not directly related to the issue, but I thought I'd not that you don't
have to have sudo exec an su with the "sudo su - user", you can get an
interactive shell from sudo directly: sudo -i -u user
-i says you want an interactive login shell. If you don't specify "-u
username" then it assumes root
11 matches
Mail list logo
