fork: retry: Resource temporarily unavailable

Donovoi commented 2 years ago

If you are going to suggest something, please remove the following template.

Issue description

Trying to run script on very resource limited red hat box. When I run ulimit -a nothing is unlimited.

Is there a way to run this awesome script without hitting that resource limit (and with very limited permission as im on the box as a webserver)

Also curl and wget will not work as this box will not accept any ssl/tls certificate (I don't think its been updated since 2010 or earlier). But I have managed to access an FTP for uploading/download files.

The logo works, and everything works up until we actually start to do some checks then I get the above error

Which parameters did you use for executing the script and how did you execute it?

I tried the silent parameter and also the -a param both with the same result

If winpeas, did you use a clean or obfuscated winpeas, and for which architecture?

Is there any AV / Threat protection in the system?

Not that I know of

Please, indicate the OS, the OS version, and the kernel version (build number in case of Windows)

Linux version 2.6.18-439.el5PAE (mockbuild@x86-vm-30.build.eng.bos.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-55))

Please, indicate the check that is failing and add a screenshot showing the problem

How did you expect it to work?

To run or to only use one thread if resource limited

Additional details / screenshot

carlospolop commented 2 years ago

Hi @Donovoi, This looks interesting, but with this info and without being able to do some tests I don't know what to say. Linpeas uses 1 thread in 99% of the script so I don't think that's the problem. Could you somehow share the machine or a link to download a VM where the same error is occurring?

Donovoi commented 2 years ago

Hi Carlos,

Thank you for your reply. It does sound like a good one to investigate.

Unfortunately I can't share the machine or create it as a VM.

What I can do is either share my screen, or relay to you the results of any tests you would need to perform.

I'm really sorry about that and totally understand if you would like to close the issue instead.

carlospolop commented 2 years ago

Could you try to find what is the first line that stops the execution of linpeas?

Donovoi commented 2 years ago

Hi Carlos,

Sorry for all the trouble. I tried to debug the shell script remotely (my first time debugging shell script) but I couldn't get any line numbers

the last line that it wrote to the console was:

sed -r 's,4.4.0-1009-raspi2|4.4.0-1012-snapdragon|4.4.0-21-generic|4.4.0-21-generic-lpae|4.4.0-21-lowlatency|4.4.0-21-powerpc-e500mc|4.4.0-21-powerpc-smp|4.4.0-21-powerpc64-emb|4.4.0-21-powerpc64-smp|4.4.0-22-generic|4.4.0-22-lowlatency|4.4.0-24-generic|4.4.0-24-lowlatency|4.4.0-28-generic|4.4.0-28-lowlatency|4.4.0-31-generic|4.4.0-31-lowlatency|4.4.0-34-generic|4.4.0-34-lowlatency|4.4.0-36-generic|4.4.0-36-lowlatency|4.4.0-38-generic|4.4.0-38-lowlatency|4.4.0-42-generic|4.4.0-42-lowlatency,&,'

I was able to turn my shell in to an ssh which is much more stable and is currently running the script without an issue.

I'm not sure if you want to close this or if you would prefer I do some further debugging, I'm more than happy.

Thanks for your time.

carlospolop commented 2 years ago

If it worked correctly inside a ssh session then I'm going to close this. However, feel free to share here more information about what was happening as this may help people in the future

peass-ng / PEASS-ng