I have recently transitioned from solo development to beta testing for a Mojolicious::Lite application. Upon this transition, I switched from my casual use of morbo to hypnotoad. In order to not change my nginx configuration, I had hypnotoad listen on port 3000. The application appeared and I made my beta testers aware of its existence and went to bed. Some time the next day, I got word of failures. When I tried to connect to the application, I could connect but I was unable to access database objects correctly. The Mojolicious::Lite script is named setupTransfer.pl. There were many tens of processes named setupTransfer.pl running on the server. I attempted hypnotoad --stop setupTransfer.pl, but it failed with an error on Time::Piece. I rather inelegantly killed all the setupTransfer.pl processes and hypnotoad. I checked my script for errors, and found nothing salient. I restarted hypnotoad, and all appeared to be working, but within a few hours setupTransfer.pl processes started to proliferate, apparently without bound. I have stopped and restarted hypnotoad several times since. For fear that this is a consequence of some confusion because of making hypnotoad listen on port 3000, I have changed my nginx configuration and switched to port 8080. Clearly I am ignorant, and doing something stupid, but cursory documentation checks have not pointed out my error. hypnotoad starts with an initial inventory of setupTransfer.pl processes of 9, and they appear to increase monotonically with activity. The server (a fairly lightweight ec2 instance) starts to exhibit problems somewhere in the 60 or 70 range.
What stupid thing am I doing?