☭
I am suddenly having bad problems with my XMPP 
@aescling After doing some normal config file changes (to allow for larger file uploads), suddenly, this happens:
# /etc/rc.d/prosody start
Starting prosody.
sh: Cannot determine current working directory
sh: Cannot determine current working directory
/usr/pkg/bin/lua5.4: /usr/pkg/lib/prosody/util/async.lua:159: /usr/pkg/lib/prosody/util/paths.lua:11: attempt to index a nil value (local 'parent_path')
stack traceback:
/usr/pkg/lib/prosody/util/paths.lua:11: in function 'prosody.core.configmanager.resolve_relative_path'
/usr/pkg/lib/prosody/util/startup.lua:330: in function 'prosody.util.startup.chdir'
/usr/pkg/lib/prosody/util/startup.lua:937: in function 'prosody.util.startup.prosody'
/usr/pkg/lib/prosody/util/async.lua:161: in function 'prosody.util.async.default_runner_func'
/usr/pkg/lib/prosody/util/async.lua:149: in function </usr/pkg/lib/prosody/util/async.lua:147>
stack traceback:
[C]: in function 'error'
/usr/pkg/lib/prosody/util/async.lua:159: in local 'handler'
/usr/pkg/lib/prosody/util/async.lua:244: in method 'run'
/usr/pkg/bin/prosody:65: in main chunk
[C]: in ?
At least, running prosodyctl start --force works instead, but still, this is bad and this didn't happen yesterday
As a total idiot, I thought that I might try updating the Prosody to fix it
That just made things worse, I need the version from pkgsrc and not the binary package, so now I am slowly slowly slowly making my tiny Raspberry Pi fetch a fresh pkgsrc over CVS...
unsolicited pawsible advice?
@vaporeon_ strange
having had issues like this befur with my synapse config when i still used it, i would guess there’s a small error in your config that is technically syntactical but nonsensical, leading to this unhelpful explosion of an error message
sometimes it was subtle enough that all i could do was recreate the config from scratch and then furget diff(1) exists and silently ponder what subtle error i could not detect from the busted config
