Are you using Apache::Reload? Try disabling that. It does things that are a bit... hinky; so sometimes things go wrong.
| [reply] |
I wasn't aware of using it. I went through my config, including apache2.conf, everything under mods-enabled, sites.enabled, conf.d, etc. both manually and using grep and was unable to find any reference to it. However, I found package libapache2-reload-perl installed on my system. I uninstalled it, restarted Apache and haven't seen the issue reoccur. Thanks to you and the other responders.
| [reply] |
Which Dancer environment are you running in? "development" or "production"? Check the corresponding file in enviroments/ for the value of auto_reload. It should be 0, but the "attempt to reload" makes me suspect that it may be enabled.
As for why it's happening, my theory would be that your program works fine the first time it's run in a specific apache child process, but then subsequent requests to the same child (presumably incorrectly) detect that unite.pm has changed and attempt to reload it, which fails. But that's just a half-assed theory since the details of your situation are a little sparse. | [reply] [d/l] [select] |
If this is an Apache configuration error then it's obviously off topic here and I'll be happy to request assistance in a more appropriate forum. But since the error is a Perl module load error, I though I'd start here. Does it matter?
How can I reproduce this problem?
| [reply] |