Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore
On 14/11/2014 20:44, Helmut Jarausch wrote:
> On 11/14/2014 06:46:28 PM, Alan McKinnon wrote:
>> On 14/11/2014 18:18, Helmut Jarausch wrote:
>>> On 11/13/2014 09:05:50 PM, Alan McKinnon wrote:
On 13/11/2014 18:41, Helmut Jarausch wrote:
> Hi,
>
> after upgrading from syslog-ng-3.5.6 to syslog-ng-3.6.1 my
>> system
has
> stopped logging, i.e. I only get the messages
> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down;
> version='3.6.1'
> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up;
> version='3.6.1'
>
> Has anybody observed the same problem, and how to fix it?
>
> Many thanks for a hint,
> Helmut
>
>
Run a syntax check on the config file, I don't have a man page to
hand
but it's quite obvious what the option is.
syslog-ng has sometimes been picky about version numbers in the
>> past
and
it's tagged in the config file. Read the syntax check output
carefully
to see if anything is amiss.
>>>
>>> Thanks, Alan.
>>>
>>> The only unusual message is
>>> Systemd is not detected as the running init system;
>>>
>>> which is true since I still use openrc (but with systemd installed,
>> as
>>> well)
>>> Could this be the culprit?
>>
>>
>> I doubt it, I also use 3.6.1 without systemd.
>>
>> Please post eix syslog-ng so we can see how your USE is set up, and
>> your
>> syslog-ng.conf
>>
> Thanks, Alan.
>
> [U] app-admin/syslog-ng
> Available versions: 3.4.7^t 3.4.8^t (~)3.5.6^t{tbz2}[1]
> (~)3.6.1^t{tbz2} {amqp caps dbi geoip ipv6 json mongodb pacct +pcre
> redis smtp spoof-source ssl systemd tcpd}
> Installed versions: 3.5.6^t{tbz2}[1](05:21:52 PM 11/14/2014)(ipv6
> json pcre ssl systemd tcpd -amqp -caps -dbi -geoip -mongodb -pacct -
> smtp -spoof-source)
> Homepage:http://www.balabit.com/network-security/
> syslog-ng
> Description: syslog replacement with advanced filtering
> features
I don't find any info on what the syslog-ng ebuild does with
USE=systemd, I suspect it may want to use the fancy logging features
built into systemd.
Since you have it, but don't run it, does USE=-systemd fix the issue?
>
> And here are the config files (I've left out the commented lines)
>
> /etc/syslog-ng/scl.conf =
> @define scl-root "`syslog-ng-data`/include/scl"
> @define include-path "`include-path`:`syslog-ng-data`/include"
>
> @include 'scl/system/plugin.conf'
> @include 'scl/pacct/plugin.conf'
> @include 'scl/syslogconf/plugin.conf'
>
> /etc/syslog-ng/syslog-ng.conf =
> options {
> threaded(yes);
> chain_hostnames(no);
> stats_freq(43200);
>
> mark_freq(3600);
> };
>
> source src { system(); internal(); };
>
> destination messages { file("/var/log/messages"); };
> destination console_all { file("/dev/tty12"); };
> log { source(src); destination(messages); };
> log { source(src); destination(console_all); };
>
>
> /etc/conf.d/syslog-ng =
> SYSLOG_NG_OPTS=""
That all looks normal, I don't see anything problematic there
--
Alan McKinnon
alan.mckin...@gmail.com
[gentoo-user] Mythtv artwork issues
Hi all, Back when I was running 0.26, mythtv would automatically download cover art, banners, and wallpaper. Since upgrading to 0.27, this hasn't happened. I did discover that 0.26 was dropping everything into the default storage group (i.e. my recordings directory) and the grabber was complaining about writes. So I've set up separate storage groups for each one, each being in their own directory. I manually ran: `mythmetadatalookup --refresh-all-rules` `mythmetadatalookup --refresh-all` `mythmetadatalookup --refresh-all-artwork` And it did update coverart, but no banners or fanart. I can go into recording rules and do this manually, but even if I set the banners and fanart and go to the watch recordings screen the only things shown in the cover art (DVD cover). Is the fanart/cover art/banners all retrieved automatically by the backend? I'm using the Arclight theme and I remember all of this working without intervention. I'm just curious to know what went wrong and if someone else bumped across this issue. I ran mythfrontend from the console and no errors appear. The backend log lists this: 2014-11-14 19:56:36.742166 W [9776/10185] ProcessRequest ringbuffer.cpp:658 (Start) - RingBuf(/mnt/mythstorage/fanart//ttvdb.py_257655_fanart.jpg): Not starting read ahead thread, this is a write only RingBuffer The backend and frontend are separate, could this be an issue sending the artwork from the backend to the frontend? Dan
Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore
On Thu, 13 November 2014, at 4:41 pm, Helmut Jarausch wrote: > > after upgrading from syslog-ng-3.5.6 to syslog-ng-3.6.1 my system has > stopped logging, i.e. I only get the messages > Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; > version='3.6.1' > Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; > version='3.6.1' There's been some activity on bugs.gentoo.org about this. Stroller.
Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore
On 11/14/2014 12:46 PM, Alan McKinnon wrote: > On 14/11/2014 18:18, Helmut Jarausch wrote: >> The only unusual message is >> Systemd is not detected as the running init system; >> >> which is true since I still use openrc (but with systemd installed, as >> well) >> Could this be the culprit? > I doubt it, I also use 3.6.1 without systemd. But did you miss that: a) he has it installed, and b) he gets a message about 'systemd is not detected as the running init system' ? Maybe it is trying to use systemd but since it isn't running?
[gentoo-user] Re: qt5
Michael Vetter uni-konstanz.de> writes: > Recently I started developing on LXQT. As they are using Qt5 on their > developing version I added Qt overlay and unmasked Qt5. BGO 525410 has some gentoo specific comments on lxqt-0.8.0 (qt5). I'm using slim as DM and openbox as WM right now. I got no problems with the clock, panel, vt switching and also no segfaults at configuring or such... Seems to be quite usable! File a gentoo bug, after you seek resolution at the lxde main site? >From what I've read, lxqt-0.8.0 is strictly qt5; some problems exist if trying to support both qt4 and qt5. But you need to check with folks running the latest codes for lxqt. [1] Last, I do not remember what is holding up the current masking of lxqt-0.8.0 but it could be related to your problem? good hunting! James [1] http://qt-project.org/wiki/Category:Tools::QtCreator#0bf259ca3118b8153806bc09bd6e84f3
[gentoo-user] apcupsd to recycle power
I have an APC SC620I, which in case of power failure, it successfully initiates a shutdown to the connected (via SMART cable) PC, but if the mains power returns, the UPS does not recycle the power to the PC, and consequently the PC stays off. Regardless if the mains power returns soon after the UPS has initiated a shutdown to the PC, shouldn't the UPS recycle the power anyway, so that the PC comes back on as set in BIOS? Am I missing something in the configuration or the daemons that should be running? (Running sys-power/apcupsd-3.14.8-r2) /etc/apcupsd/apcupsd.conf folows: UPSNAME SC620I UPSCABLE smart UPSTYPE apcsmart DEVICE /dev/ttyS0 LOCKFILE /var/lock SCRIPTDIR /etc/apcupsd PWRFAILDIR /etc/apcupsd NOLOGINDIR /etc ONBATTERYDELAY 6 BATTERYLEVEL 20 MINUTES 2 TIMEOUT 0 ANNOY 300 ANNOYDELAY 60 NOLOGON disable KILLDELAY 0 NETSERVER on NISIP 192.168.0.1 NISPORT 3551 EVENTSFILE /var/log/apcupsd.events EVENTSFILEMAX 10 UPSCLASS standalone UPSMODE disable STATTIME 600 STATFILE /var/log/apcupsd.status LOGSTATS off DATATIME 0 BATTDATE 10/17/11 SENSITIVITY H WAKEUP 60 SLEEP 180 LOTRANSFER 208 HITRANSFER 253 RETURNCHARGE 45 BEEPSTATE L LOWBATT 5 OUTPUTVOLTS 230 SELFTEST 336
Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore
On 11/14/2014 06:46:28 PM, Alan McKinnon wrote:
> On 14/11/2014 18:18, Helmut Jarausch wrote:
> > On 11/13/2014 09:05:50 PM, Alan McKinnon wrote:
> >> On 13/11/2014 18:41, Helmut Jarausch wrote:
> >>> Hi,
> >>>
> >>> after upgrading from syslog-ng-3.5.6 to syslog-ng-3.6.1 my
> system
> >> has
> >>> stopped logging, i.e. I only get the messages
> >>> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down;
> >>> version='3.6.1'
> >>> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up;
> >>> version='3.6.1'
> >>>
> >>> Has anybody observed the same problem, and how to fix it?
> >>>
> >>> Many thanks for a hint,
> >>> Helmut
> >>>
> >>>
> >>
> >>
> >> Run a syntax check on the config file, I don't have a man page to
> >> hand
> >> but it's quite obvious what the option is.
> >> syslog-ng has sometimes been picky about version numbers in the
> past
> >> and
> >> it's tagged in the config file. Read the syntax check output
> >> carefully
> >> to see if anything is amiss.
> >
> > Thanks, Alan.
> >
> > The only unusual message is
> > Systemd is not detected as the running init system;
> >
> > which is true since I still use openrc (but with systemd installed,
> as
> > well)
> > Could this be the culprit?
>
>
> I doubt it, I also use 3.6.1 without systemd.
>
> Please post eix syslog-ng so we can see how your USE is set up, and
> your
> syslog-ng.conf
>
Thanks, Alan.
[U] app-admin/syslog-ng
Available versions: 3.4.7^t 3.4.8^t (~)3.5.6^t{tbz2}[1]
(~)3.6.1^t{tbz2} {amqp caps dbi geoip ipv6 json mongodb pacct +pcre
redis smtp spoof-source ssl systemd tcpd}
Installed versions: 3.5.6^t{tbz2}[1](05:21:52 PM 11/14/2014)(ipv6
json pcre ssl systemd tcpd -amqp -caps -dbi -geoip -mongodb -pacct -
smtp -spoof-source)
Homepage:http://www.balabit.com/network-security/
syslog-ng
Description: syslog replacement with advanced filtering
features
And here are the config files (I've left out the commented lines)
/etc/syslog-ng/scl.conf =
@define scl-root "`syslog-ng-data`/include/scl"
@define include-path "`include-path`:`syslog-ng-data`/include"
@include 'scl/system/plugin.conf'
@include 'scl/pacct/plugin.conf'
@include 'scl/syslogconf/plugin.conf'
/etc/syslog-ng/syslog-ng.conf =
options {
threaded(yes);
chain_hostnames(no);
stats_freq(43200);
mark_freq(3600);
};
source src { system(); internal(); };
destination messages { file("/var/log/messages"); };
destination console_all { file("/dev/tty12"); };
log { source(src); destination(messages); };
log { source(src); destination(console_all); };
/etc/conf.d/syslog-ng =
SYSLOG_NG_OPTS=""
Re: [gentoo-user] difficulties with lvm2+systemd+grub2
On Wed, Nov 12, 2014 at 11:20:53AM +0100, Stefan G. Weichinger wrote: > Am 12.11.2014 um 11:07 schrieb Sam Jorna: > > On Wed, Nov 12, 2014 at 10:42:28AM +0100, Michael Mair-Keimberger > > wrote: > >> On Wed, Nov 12, 2014 at 12:03:04PM +1100, wra...@wraeth.id.au > >> wrote: > >>> On Tue, Nov 11, 2014 at 09:56:09PM +0100, Michael > >>> Mair-Keimberger wrote: > > > >> systemd. Maybe i could adopt that to my custom one as well. > > > > > > Working examples are always nice :-) > > Around dracut and grub2 I remember a few bits, maybe they help. > > In /etc/dracut.conf I have (after discussion here): > > # dracut modules to omit > omit_dracutmodules+="systemd" > > (this one means "don't build an instance of systemd *into* the initrd) > > # dracut modules to add to the default > add_dracutmodules+="bash" > > # build initrd only to boot current hardware > hostonly="yes" > hostonly_cmdline="yes" > > I don't use lvm and sw-raid anymore, you might need: > > add_dracutmodules+="lvm bash mdraid" > > or so. > > After playing around some more hours with initram's i've finally found out what my problem was. It is easier than I though :D Basically my changes in my grub config were already correct, however I completely forgot, that, since I wrote my own init script, arg's like "root" and "init" simply weren't used by my script... If you look at my script, I only check the cmdline for "lvm", so setting "init" or "root" haven't any effect at all :D That means, after modifying my init script, using "/usr/lib/systemd/systemd" as init, systemd booted up. It's still not perfect - it looks like it can't mount other lvm partition's and thus only boot's into maintains mode - but it boot's :) Regarding dracut: Even though I got it to work, it also just bootet openrc and not systemd. Don't know why and I didn't digged further after it worked with my own script. Regarding LVM: As mentioned systemd can't mount my lvm partitions from fstab. Those lvm partitions should be mounted by UUID, but it seems like systemd can't find them, even though there are available afterwards (under /dev/vg0/...). If I comment them out in /etc/fstab (they are not important) systemd boots just fine. I've also set "use_lvmetad = 1" in /etc/lvm/lvm.conf as mentioned at the systemd wiki. Any clue why that doesn't work? -- greetings Michael Mair-Keimberger signature.asc Description: Digital signature
[gentoo-user] Re: question regarding usb gadget / eth usb
gmx.de> writes: > Hi James :) > ...ARM9 emulator...nice idea. > Does such thing exists for Linux? http://www.thefreecountry.com/emulators/arm.shtml > > Good hunting! > ...thanks! Your good wish has already worked! > I got access to the board 8) I'm always glad to hear of your successes It looks like the "arm9" is a moderized "Arm Thumb" processor. ARM926EJ-S™ ARM® Thumb® Processor So there is a rich archives of codes for the arm thumb. Exactly what the new processor you have on your new board compared to the legacy features of the "Arm Thumb" is something you are going to have to research, test and verify. Arm codes from older devices usually run on newer arm processors, but not always. Indianess and similar issue abound, but they are usually well documented, including examples. https://www.linaro.org/projects/ Linaro is moving arm linux, particularly but not limited to 64bit arm, forward at light speed. It is a formidable collection of coders. Many have connections to the legacy arm communities, like the Arm Thumb. Much of the Arm Thumb legacy codes will run natively on the Aarch64 Arm processors. Im pretty sure you'll be able to run an Aarch64 arm chip like a cluster of arm thumb procesors. Aarch64 is purported to support 2 or 3 simultaneously running and different Operating Systems, concurrently. It is a brave new world and arm is the place to be. Even AMD has several Arm (64 bit)server SOC in the process of being rolled out! > Best regards, > Meino James
Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore
On 14/11/2014 18:18, Helmut Jarausch wrote: > On 11/13/2014 09:05:50 PM, Alan McKinnon wrote: >> On 13/11/2014 18:41, Helmut Jarausch wrote: >>> Hi, >>> >>> after upgrading from syslog-ng-3.5.6 to syslog-ng-3.6.1 my system >> has >>> stopped logging, i.e. I only get the messages >>> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; >>> version='3.6.1' >>> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; >>> version='3.6.1' >>> >>> Has anybody observed the same problem, and how to fix it? >>> >>> Many thanks for a hint, >>> Helmut >>> >>> >> >> >> Run a syntax check on the config file, I don't have a man page to >> hand >> but it's quite obvious what the option is. >> syslog-ng has sometimes been picky about version numbers in the past >> and >> it's tagged in the config file. Read the syntax check output >> carefully >> to see if anything is amiss. > > Thanks, Alan. > > The only unusual message is > Systemd is not detected as the running init system; > > which is true since I still use openrc (but with systemd installed, as > well) > Could this be the culprit? I doubt it, I also use 3.6.1 without systemd. Please post eix syslog-ng so we can see how your USE is set up, and your syslog-ng.conf -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore
On 11/13/2014 09:05:50 PM, Alan McKinnon wrote: > On 13/11/2014 18:41, Helmut Jarausch wrote: > > Hi, > > > > after upgrading from syslog-ng-3.5.6 to syslog-ng-3.6.1 my system > has > > stopped logging, i.e. I only get the messages > > Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; > > version='3.6.1' > > Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; > > version='3.6.1' > > > > Has anybody observed the same problem, and how to fix it? > > > > Many thanks for a hint, > > Helmut > > > > > > > Run a syntax check on the config file, I don't have a man page to > hand > but it's quite obvious what the option is. > syslog-ng has sometimes been picky about version numbers in the past > and > it's tagged in the config file. Read the syntax check output > carefully > to see if anything is amiss. Thanks, Alan. The only unusual message is Systemd is not detected as the running init system; which is true since I still use openrc (but with systemd installed, as well) Could this be the culprit? Helmut
Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore
On Thursday, November 13, 2014 05:41:27 PM Helmut Jarausch wrote: > Hi, > > after upgrading from syslog-ng-3.5.6 to syslog-ng-3.6.1 my system has > stopped logging, i.e. I only get the messages > Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; > version='3.6.1' Here it stops > Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; > version='3.6.1' Here it starts > Has anybody observed the same problem, and how to fix it? See above. -- Joost
[gentoo-user] qt5
Hello, Recently I started developing on LXQT. As they are using Qt5 on their developing version I added Qt overlay and unmasked Qt5. I should add normally I am more the GTK applicatio user, running i3 as window manager. So Qt and its configuration are kind of new to me. Anyways, I got LXQT to run and started hacking. However I thought a IDE would be nice. So I installed Qtcreator. All applications so far (example: pcmanfm-qt using Qt5) are looking good. But Qtcreator looks awful: grey font on white background and whitefont on black background. I wondered why this was the case, and after checking with ldd I realized that Qtcreator uses Qt4. I tried to run qtconfig and choose a nice theme, as I was used to with lxappearance for GTK. However, no matter what I selected in "Select GUI style", the colors stayed ugly. I tried Cleanlooks, Qtcurve and others. Then I saw that I can manually change color palette. This is strange, on GTK themes come with nice colors without selecting them by hand. Am I doing something wrong? So I have several questions: 1. How to configure Qt4 themes/colors the right way? 2. Can I remove Qt4 totally and only use Qt5 for all applications? I am aware that Qt5 is not stable, but the mask says its more orless table but masked for doing more tests. Also I didn't see a USE flag for Qtcreator, no Qt4 no Qt5. 3. For testing I wanted to add gtkstyle USE flag to qtgui, then realized that this doesn't exist anymore for Qt5. But Qtcreator seems to be compiled for Qt4, so how to set gtkstyle for it? 4. Has Qt5 also the possibility to have gtkstyle? I am thankful for all info I can get, also background information for understanding everything totally, since this is the main goal of writing this mail. best regards, Michael
Re: [gentoo-user] Re: gcc 4.7.3 --> 4.8.3
On Thu, 13 Nov 2014 23:52:22 -0500, Jonathan Callen wrote: > > Yes, things may be a little different with 4.9, but the last time a > > rebuild was really required was,AFAIR, somewhere around 3.3. > The last time a rebuild of (almost) everything was required was when > the C++ ABI changed, with the associated bump of SONAME from > libstdc++.so.5 (provided with GCC 3.3 and earlier) to libstdc++.so.6 > (provided with GCC 3.4 and later). So you were close, but the major > change happened with 3.4, not 3.3 ;). Obviously, I meant FROM 3.3 :P ;-) -- Neil Bothwick I'm writing a book. I've got the page numbers done. pgpsjZj6CmqAK.pgp Description: OpenPGP digital signature
