| Summary: | SSH slowdown on 147.75.85.211 and 147.75.85.214 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Adam Farley <adfarley> | ||||
| Component: | Servers | Assignee: | Mikaël Barbero <mikael.barbero> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | denis.roy, mikael.barbero, sxa | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 10 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Adam Farley
P.S. The slowdown and process launching issues are blocking all work on Solaris x86. > uptime output:
> 1:44pm up 99 day(s), 20:42, 2 users, load average: 4282.57, 4858.22,
> 5379.39
Would top be helpful in finding which process(es) are hogging the system?
Unfortunately, top isn't a command the Solaris x86 systems recognize. A website recommended "prstat -a", but that failed to run: -bash-3.2$ prstat -a -bash: fork: Resource temporarily unavailable If it helps, ps -ef still works, and I stuck the output into a file. ps_output.txt, attached. Created attachment 287274 [details]
ps output from 147.75.85.211
I have the `ps` listing from the machine - there is an "obvious" problem with processes owned by root (therefore out of our control) which needs addressing by the Eclipse sysadmins :-) I4m looking into it as we speak. These two machines were compromised, and will not be coming back. We're investigating -- we'll prepare a report. We'll revise our processes for validating machines before adding them machines to the build process. I suggest new ones be rebuilt. Thanks Denis & Mikael. After consulting with the team, it seems a good idea for us to wait until the report is ready before adding more solaris x86 machines to the pool. That way we can be confident that the new machines avoid the issue/s that caused the old ones to be compromised. The report has been authored and reviewed, and we've circulated it to the Executive team as there are legal implications here. We'll release the report as soon as we can, as it contains a few recommendations. Thx for your patience. This has been resolved. |