u/mustang__1 — reddlx

FusionPBX fails to install/start FreePBX

Trying to get a fresh install of FusionPBX up and running and I'm running in to problems with it installing FreePBX. Installing on 24.04

checking for libpcre2-8 &gt;=  10.00... Package libpcre2-8 was not found in the pkg-config search path. Perhaps you should add the directory containing `libpcre2-8.pc' to the PKG_CONFIG_PATH environment variable Package 'libpcre2-8', required by 'virtual:world', not found
configure: error: Library requirements (libpcre2-8 &gt;=  10.00) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.
make: *** No targets specified and no makefile found.  Stop.
make: *** No rule to make target 'install'.  Stop.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
lsb-release is already the newest version (12.0-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
switch/source-sounds.sh: 84: ../environment.sh: verbose: not found
make: *** No rule to make target 'sounds-install'.  Stop.
make: *** No rule to make target 'hd-sounds-install'.  Stop.
make: *** No rule to make target 'cd-sounds-install'.  Stop.
mv: cannot stat '/usr/share/freeswitch/sounds/music/*000': No such file or directory
mv: cannot stat '/etc/freeswitch': No such file or directory
chown: cannot access '/var/lib/freeswitch': No such file or directory
chown: cannot access '/var/log/freeswitch': No such file or directory
chown: cannot access '/var/run/freeswitch': No such file or directory
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package freeswitch-systemd

reddit.com

u/mustang__1 — 3 days ago

▲ 9 r/SQLServer+1 crossposts

SqlServerWriter "Inconsistent Shadow Copy"

Started getting Veeam backup failures that I believe I've tracked down to SqlServerWriter VSS, which reports "Inconsistent Shadow Copy".

I believe this began occurring after updating SQL Server 2017 to the most current patch level (which I swear I did already but... meh).

The error occurs when trying to create a production-only backup.

I increased drive space by 150gb for each the OS drive and data drive on the SQL Server host machine. The VM host has 3x physical space utilized by the two drives (snapshot location).

Restarting the SqlServerWriter service clears the error, but starting off another production-only checkpoint fails and brings the error back.

I ran through the checklist at the end of the article here: https://www.veeam.com/kb3137 , and didn't see any failures or missteps.

The only thing I haven't done is reboot the server since I saw the errors - but since it hosts the ERP I'll need to plan that for after hours at some point.

u/mustang__1 — 10 hours ago

▲ 257 r/philly

Monday at rush hour makes sense

Seriously... Wtf was this shit about with hundreds of bikes on cops closing down Columbus? At fucking Monday rush hour?

u/mustang__1 — 4 days ago