similar to: Strange behavior in Icecast 2.44 startup

Displaying 20 results from an estimated 2000 matches similar to: "Strange behavior in Icecast 2.44 startup"

2024 Sep 19
1
Strange behavior in Icecast 2.44 startup
On 19 Sep 2024, at 22:08, Steve Matzura wrote: > I have a script that starts Icecast, waits a couple seconds, then starts ices. When I installed it all on Ubuntu 20.04, it just worked. Well, it still works now, but with a wrinkle. If I execute: > > > /etc/init.d/icecast2 start > Hi, as far as I understand ?/etc/init.d/icecast2 start? on your system just dispatches to systemctl so
2020 Jan 22
3
dbus/systemd failure on startup (CentOS 7.7)
We are seeing a problem that occurs ~5% of the time when rebooting CentOS 7.7 where systemd gets a 'Connection timed out' to D-Bus just after the D-Bus service starts - from 'journalctl -x' : ... Jan 21 16:09:59 linux7-7.mpc.local systemd[1]: Started D-Bus System Message Bus. -- Subject: Unit dbus.service has finished start-up -- Defined-By: systemd -- Support:
2020 Jan 23
2
dbus/systemd failure on startup (CentOS 7.7)
Simon Matter via CentOS wrote: > >> We are seeing a problem that occurs ~5% of the time when rebooting > > I see such issues on a quite large multi user system but when this > happens, after forced restarts for kernel updates, I usually don't have > the time to analyze and play doctor on it. My "solution" now is to simply > reboot the server again in such a
2019 Aug 11
2
Can't replicate DCs
Hi list, I'm running into issues with Samba 4.5.16-Debian. I am trying to get 3 DCs to talk to each other and replicate. DC1 and DC3 are on the same subnet; DC2 is on another subnet, accessible by IP. Currently, no firewalls on any of the DCs. Issue 1 - When I run "samba-tool drs showrepl", I get various results: DC1 - Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2
2020 Jan 23
0
dbus/systemd failure on startup (CentOS 7.7)
> We are seeing a problem that occurs ~5% of the time when rebooting I see such issues on a quite large multi user system but when this happens, after forced restarts for kernel updates, I usually don't have the time to analyze and play doctor on it. My "solution" now is to simply reboot the server again in such a case, AKA the systemd way :-) > CentOS 7.7 where systemd gets
2020 Jan 23
0
dbus/systemd failure on startup (CentOS 7.7)
> Simon Matter via CentOS wrote: >> >>> We are seeing a problem that occurs ~5% of the time when rebooting >> >> I see such issues on a quite large multi user system but when this >> happens, after forced restarts for kernel updates, I usually don't have >> the time to analyze and play doctor on it. My "solution" now is to >> simply
2017 Apr 05
2
CentOS 7, systemd,, and message floods
I've just updated a couple of servers, latest 7.3, and systemd is flooding dmesg, journalctl with info level messages... or maybe debug level 1. Examples: [ 478.258571] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=436 reply_cookie=0 error=n/a [
2020 Sep 22
1
Login failure with Secure Boot
Hi all, I have a laptop in UEFI mode running CentOS 8.2. All works fine but when I enable Secure Boot, login via gdm is no longer possible. Console login is ok. I found some related discussions over on Ubuntu forums, suggesting that this could be related to 3rd-party kernel modules, such as nvidia. This laptop has only Intel builtin graphics, and every single module installed is part of the
2024 Sep 20
1
EZstream XML that used to work
This is about as simple as it can get. It worked earlier today. I added a couple lines, like sample rate and channels, it stopped working so I took them out, and now when I run it through /usr/bin/ezstream with the '-c' option, I get: ezstream[5609]: ezstream/shout.xml: world readable??? # that's normal ezstream[5609]: stream: default: no configuration Here's the XML, with
2013 Dec 03
2
error: Failed to start domain
On a gentoo server with libvirt-1.1.3 I get problems with starting VMs. When I do: # virsh start vm180 error: Failed to start domain vm180 error: Input/output error This happens with 1.1.3 and 1.1.4 (I rebuilt the packages and restarted the libvirtd.service). # journalctl -f -u libvirtd.service shows: Dec 03 17:32:56 jupiter libvirtd[24020]: Input/output error Dec 03 17:33:47 jupiter
2024 Jun 05
1
LLM GPU Support
On Tue, 2024-06-04 at 10:27 -0500, Blake McBride wrote: > Greetings, > > I have used the nouveau driver with my Nvidia card on Linux.? Works > fine.? However, my problem has to do with running LLM on my GPU with > your driver.? My impression is, it doesn't work.? Am I correct? Yo, "it doesn't work" is not a very precise error description. The maintainers will
2013 Dec 03
0
Re: error: Failed to start domain
Am 03.12.2013 17:36, schrieb Stefan G. Weichinger: > > On a gentoo server with libvirt-1.1.3 I get problems with starting VMs. Additional logs: # journalctl -f lists Dec 03 18:19:31 jupiter systemd-machined[23995]: Failed to start machine scope: Method "StartTransientUnit" with signature "ssa(sv)" on interface "org.freedeskt...sn't exist Dec 03 18:19:31
2008 Dec 01
4
msg 14 (WM_ERASEBKGND) not supported yet
Greetings, I have a Win32 app I wrote in C. I compiled the source code for Wine without a problem. The app appears to run fine but it spits out: fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet I checked all of my code and nowhere do I use WM_ERASEBKGND. Can someone give me a hint on how to get rid of this annoying message? Thank you. Blake McBride -------------- next
2017 Feb 17
0
Centos 7: .tons of messages logs (systemd-logind[663]: Got message type....)
On my Centos 7 update, into "journalctl -f" I have tons of this kind of message > feb 17 23:52:09 s-ispc.local systemd-logind[663]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=17152 reply_cookie=0 error=n/a > feb 17 23:52:09 s-ispc.local
2006 Nov 28
1
Can't drop root group privileges
Hi all, I need your insight. I've been testing Dovecot on an AIX 5.2 system. Compiled and running fine. We have some users on an AIX 5.1 system, so I'm working on installing it there, so we can do further testing. I'm using Dovecot 1.0 RC15 with OpenSSL 9.0.7e, configured to use port 10143 (imap) and 10993 (imaps). The error I'm seeing in the log is: dovecot: Nov 28
2006 Mar 30
1
Predict function for 'newdata' of different dimension in svm
I am using the "predict" function on a support vector machine (svm) object, and I don't understand why I can't predict on a dataset with more observations than the training dataset. I think this problem is a generic "predict" problem, but I'm not sure. The original svm was fit on 50 observations.
2010 May 28
2
[LLVMdev] Nightly build of CMake with clang 1.1
Hi all, (1st time post, I hope this is on topic...) I notice that CMake is listed as one of the C++ projects that clang can build: <http://clang.llvm.org/cxx_status.html> I thought I'd pass on that I've created a nightly build of CMake that uses clang 1.1 (from llvm 2.7) <http://www.cdash.org/CDash/index.php?project=CMake> (search for 'clang') It does build, but...
2024 Jun 04
1
LLM GPU Support
Greetings, I have used the nouveau driver with my Nvidia card on Linux. Works fine. However, my problem has to do with running LLM on my GPU with your driver. My impression is, it doesn't work. Am I correct? Given today's environment, this may be a good FAQ. Thanks! Blake McBride -------------- next part -------------- An HTML attachment was scrubbed... URL:
2006 Sep 21
6
Dovecot Usage Poll
Hi all, I'm trying to get a feel for how many sites are using Dovecot and the size of the installation. Jonathan's query about big sites spurred my curiousity. I'd like to take an informal poll and will post results to the list. I'm interested in hearing from those of you who are using dovecot in a real-life/production type environment (not just testing). Please email me
2008 Oct 13
2
Compatibility namespaces containing a leading ~ appear to be broken in 1.1.x
Greetings, I'm building a new 1.1.x-series Dovecot installation, and I have a problem setting up compatibility namespaces intended to handle old client-side settings. (See also: http://wiki.dovecot.org/Namespaces#head-0f3ab5ecab632eb517866c3508021e0605d54d4d) I have produced a slightly cut-down example configuration which demonstrates the problem: # dovecot -n # 1.1.3: