Vaporeon :vaporeon: ☭

I am suddenly having bad problems with my XMPP :blobcatsadreach:

1
æʃliŋ, ring racers purropawgandist
Follow

@vaporeon_ oh no :blobmeow_sadforereach:​

· · 1 · 0 · 1
Vaporeon :vaporeon: ☭

@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...

1+
Vaporeon :vaporeon: ☭

@aescling Restoring the old config doesn't fix it, I've checked

What's irritating is that yesterday, everything ran fine, this is very irritating and even suspicious (hardware failure? system got hacked?) HOW DOES THIS HAPPEN IF I DIDN'T TOUCH ANYTHING SINCE YESTERDAY

1+
Vaporeon :vaporeon: ☭

@aescling I'm sorry, @wallhackio , you getting your big PDF is delayed until I fix whatever this is...

1
Bumby the Loaf

@vaporeon_ @aescling there is no rush, really. im busy right now so i wouldn't be able to read it anytime soon so take your time

1
*
æʃliŋ, ring racers purropawgandist

@wallhackio @vaporeon_ you say that, but if you were self hosting social networking software that you actively use right now, and it had a broken configuration, i can tell you from direct experience that you would understand that the need to fix that Immediately eats away at your very soul lmao

1
Vaporeon :vaporeon: ☭

@aescling @wallhackio Yeah :/
At least, I am distracting myself by listening to my friends the Onfies talk about Game Boy programming while I wait for the CVS update to complete...

0
æʃliŋ, ring racers purropawgandist

@vaporeon_ w e i r d

1+
æʃliŋ, ring racers purropawgandist

@vaporeon_ sorry i missed your second toot at furst

1
Vaporeon :vaporeon: ☭

@aescling Now that you mention it, I'm actually not 100% sure whether I restored the old config, I'll test again once I have restored the correct version from pkgsrc, this will take quite a long time, though

0
Vaporeon :vaporeon: ☭

@aescling Regarding why I need the version from pkgsrc: The binary package on NetBSD, it has a bug that prevents the cryptography module from being loaded and therefore no file uploads... This is fixed in pkgsrc, but stupidly I restored the binary package because I forgot about it...

0
æʃliŋ, ring racers purropawgandist

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

0
Sign in to participate in the conversation
📟🐱 GlitchCat

A small, community‐oriented Mastodon‐compatible Fediverse (GlitchSoc) instance managed as a joint venture between the cat and KIBI families.

Resources

Developers

What is Mastodon?

cat.family

More…

v3.5.3+kibicat · Privacy Policy