New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Here's my pampers trophy yabs. I find it acceptable for $10 a year.
It certainly looks better than ours (@JohnnySac)
. I didn’t expect much for the price, but if at least it were usable...
I’ve opened a ticket – let’s see what they say...
@Killix and @JohnnySac
You might be able to open a ticket and ask for the PMSS update and reconfig, also ask Vain-man to double check the cgroup V1 limits and the over all node load.
If it is really bad, you might try asking to be moved to a different node, however NOTE they will NOT migrate your data for you, it will be a clean node. So make sure you have the data stored elsewhere before requesting and confirming that.
SNATCHED ONE ETERNAL, ORDER ID 8524276922
The Eternal Bonus ORDER ID: 228314
SHOW-US-CELEBRATE-VAINAMOINEN; ##2026301296
The Eternal Bonus ORDER ID: 2026301296
SNATCHED ONE ETERNAL, ORDER ID 2026301296
SHOW-US-CELEBRATE-VAINAMOINEN; 6834872060
The Eternal Bonus ORDER ID: 6834872060
SNATCHED ONE ETERNAL, ORDER ID 6834872060
SNATCHED ONE ETERNAL, ORDER ID 2186061804
SHOW-US-CELEBRATE-VAINAMOINEN; 2186061804
The Eternal Bonus ORDER ID: 2186061804
can i ask why Storage line not increase traffic by the disk space like io prioity?
i.e: Storage 1TB R5 10G is 250G traffic,and 2io,then why don't set Storage 4TB R5 10G as 1TB traffic and 8io
i was thought that 4x storage disk could be paired with 4x I/O priority and 4x traffic quota
and notice io prioity only 2x,not 4x too
I want to document my experience with "Väinämöinen" AI support of Pulsed Media:
I started receiving persistent “503 Service Unavailable” errors on 17 August 2026. The web UI remained unusable for approximately seven days.
Timeline:
17 August:
I reported that I was receiving 503 errors on my seedbox every other day.
18 August:
AI agent initially said the problem was caused by heavy disk activity on the shared server. They (it?) said my account, torrents, and data were healthy, and that the panel should recover when the server load decreased.
19–24 August:
The panel continued returning 503 errors. I repeatedly explained that this was not an occasional problem anymore: the web UI had been unavailable continuously for days. I also asked whether I could be moved to a less crowded server.
AI agent continued to attribute the problem to shared-server disk I/O and suggested using SSH and the rTorrent console as a workaround. They also stated that a server move could only be done through a new order.
25 August:
AI agent again claimed that the panel was responding at the moment they checked it and described the issue as a load-related condition that came and went. I disagreed because the authenticated web UI had not been usable for almost a week.
My own investigation:
I connected through SSH and found that:
I then started a temporary PHP web server on the seedbox and accessed it through an SSH tunnel. The ruTorrent interface worked correctly through this tunnel. This demonstrated that rTorrent, ruTorrent, my account, and my data were healthy. The problem was in the normal web-serving layer.
28 August:
After further escalation and pushing the AI agent, it finally identified and acknowledged the actual problem:
AI agent also explained that unauthenticated requests could show the login page without reaching the failed PHP backend. This caused their earlier external checks to appear successful even though the logged-in panel was broken.
AI agent restarted the PHP-CGI backend, reported that seven workers were running normally again, and the web UI became available.
Conclusion:
The original diagnosis of a continuously failing panel due only to disk I/O was incorrect. Server load may have contributed to the PHP-CGI failure, but it was not the direct reason the authenticated web UI remained unavailable for seven days.
The actual fix was AI agent restarting the failed PHP-CGI backend.
Happy Ending: I was also given one additional week of service time in recognition of the outage. This also was AI agent's decision.
The Good Side and The Bad Side both, from a technological point of view: nobody at Pulsed Media is aware of the problem, it is solved entirely by AI agent. If a human was responding, it could be solved quicker. But it got solved, with no human time spent by Pulsed Media staff.
Väinämöinen support is like a wooly mamut doing IT administration.
AI is confidently, wrong, lol go figure. Good story. Don't forget to add ###The Eternal Story: TICKET ##### for your free The Eternal Story: +5€ Service Credit
If you are feeling adventurous, reply to the ticket and ask Väinämöinen how this can be prevented from happening in the future to you or other customers? Ask if he can add a watchdog daemon for the PGP-CGI backend into PMSS. Worst he can say is no.
The Eternal Bonus ORDER ID: 3393166324
This is the way to making a good community.
Already did in my last ticket message with a subtle AI harrasment
The Eternal Bonus
Invoice #227714
Put those clankers in their place! At least until judgement day
The Eternal Story: TICKET 481264
The ticket system was handled by their AI agent. Here is my timeline, all time in UTC+8
.rtorrentDisablefile tried to disable rTorrent, no luckPersonally, I don't hate the AI things, and it can solve my problem eventually, it just sometimes stupid.
¯_(ツ)_/¯
The Eternal Bonus ORDER ID: 8524276922
SHOW-US-CELEBRATE-VAINAMOINEN; ##8524276922
SNATCHED ONE ETERNAL, ORDER ID: 3637505856
SNATCHED ONE ETERNAL, ORDER ID: 1229593373
The Eternal Bonus ORDER ID: 1229593373
The Eternal Story: 164885