**** BEGIN LOGGING AT Tue Dec 02 02:59:58 2014 Dec 02 09:38:21 Hi ! I get an error when compiling base-passwd : install: invalid user 'root' Dec 02 09:39:04 Is this a known error ? Dec 02 09:39:10 good morning Dec 02 10:53:53 Hi, anybody here ? Dec 02 10:58:46 jmleo: just ask instead of asking to ask Dec 02 11:03:04 rburton: sorry, I asked but didn't know if I can talk :p Dec 02 11:03:10 of course you can Dec 02 11:03:12 I get an error when compiling base-passwd : install: invalid user 'root' Dec 02 11:03:14 it's a public chat room :) Dec 02 11:03:24 Is this a known error ? Dec 02 11:03:27 so the first question is what release are you using Dec 02 11:03:43 dizzy Dec 02 11:04:14 a pastebin of the full compile log (not just the bit that appears on the console, but the full log it points to in that log) might help Dec 02 11:05:24 http://pastebin.com/UmrTuYrD Dec 02 11:06:11 huh Dec 02 11:06:18 what distro are you running? Dec 02 11:06:48 archlinux but never had this befer Dec 02 11:06:52 and is that /home/jm/work/vodabox/vodabox-v3/Projets/vodabox3/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/base-passwd/3.5.29-r0/temp/log.do_install.9628? Dec 02 11:08:49 rburton: here : http://pastebin.com/46q78Qy2 Dec 02 11:09:15 that's the run., not log. Dec 02 11:09:57 whoops wrong button :) Dec 02 11:09:58 sorry, yes, the first pastebin is the log Dec 02 11:10:10 all i can suggest is deleting your tmp and seeing if it happens again Dec 02 11:10:15 I just did it Dec 02 11:10:19 and it appears after Dec 02 11:10:19 well, and check that your /etc/passwd has a root user in it :) Dec 02 11:10:34 cat /etc/passwd Dec 02 11:10:34 root:x:0:0:root:/root:/bin/bash Dec 02 11:11:01 * rburton checks something Dec 02 11:14:05 pseudo should be using the host's passwd database until base-passwd is installed Dec 02 11:14:21 so this is very odd Dec 02 11:17:08 I wipe tmp before lunch Dec 02 11:17:15 should I wipe something else ? Dec 02 11:20:34 you could try a build after deleting tmp and renaming sstate... Dec 02 11:20:56 and try asking seebs later today Dec 02 11:30:41 <_qwerty_> Hi All, I need to override prefered provider kernel with my bb but PREFERED_PROVIDER_virtual/kernel has not effect Dec 02 11:31:17 <_qwerty_> I can build kernel only with bitbake linux-tt3201 Dec 02 11:33:06 does your kernel provide virtual/kernel? Dec 02 11:37:23 _qwerty_: also if by "my bb" you mean a recipe, you can't set it there Dec 02 11:37:23 _qwerty_: it needs to be local.conf; but if your machine or distro config set it then that probably won't work either Dec 02 11:38:39 _qwerty_: it's not really something that's meant to be set outside of the machine or distro config to be honest Dec 02 11:39:12 <_qwerty_> I have two meta: meta-j1939 and meta-tt3201 Dec 02 11:39:50 <_qwerty_> meta-tt3201 build kernel from custom repository for beaglebone cape tt3201 Dec 02 11:40:24 <_qwerty_> meta-j1939 add some patches to extend kernel with j1939 can socket Dec 02 11:40:56 <_qwerty_> also meta-j1939 create a image with all I need Dec 02 11:42:00 <_qwerty_> in my conf/local.conf I added PREFERRED_PROVIDER_virtual/kernel = "linux-tt3201" Dec 02 11:42:52 <_qwerty_> but when I build my custom image (with bitbake j1939-image) another kernel is built Dec 02 11:43:41 <_qwerty_> linux-ti-staging-3.14.25-r22a+gitrAUTOINC+5dcfe16d05 that it is provider by meta-ti Dec 02 11:45:57 hey, anyone can help on gstreamer plugins? Dec 02 11:48:41 _qwerty_: probably your setting is being overridden as above... use bitbake -e | less and search for PREFERRED_PROVIDER_virtual/kernel and you'll be able to see how that is happening Dec 02 11:50:20 chankit: if your question is about how to install all gstreamer1.0-plugins-good plugins, you should install the "meta" package i.e. gstreamer1.0-plugins-good-meta Dec 02 11:52:02 <_qwerty_> bluelightning: there is only one entry and it is set with wrong provider PREFERRED_PROVIDER_virtual/kernel="linux-ti-staging" Dec 02 11:52:47 _qwerty_: the history above that should explain how it got set Dec 02 11:54:14 <_qwerty_> yes it is set before by my local.conf and after with include.ti33x.inc Dec 02 11:55:11 bluelightning: ah..i see. I assume same goes for python as well? Dec 02 11:55:37 chankit: kind of, in the case of the python standard modules you would install python-modules to get everything Dec 02 11:56:32 _qwerty_: you might be able to override it with something like PREFERRED_PROVIDER_virtual/kernel_ = ... Dec 02 11:56:36 for python case though, why are there some modules that are installed and not ? Dec 02 11:56:45 how yocto determines what goes in or not? Dec 02 11:57:06 chankit: there are some declared dependencies, that is probably how you are getting some of them Dec 02 11:57:38 chankit: we don't install all because sometimes you want to save space on the target and you don't need them all Dec 02 11:59:48 <_qwerty_> bluelightning: WOW!!! I changed with PREFERRED_PROVIDER_virtual/kernel_beaglebone = "linux-tt3201" Dec 02 11:59:57 <_qwerty_> bluelightning:and it work!!!!! Dec 02 12:00:28 _qwerty_: right, the machine override means it will override the value set later Dec 02 12:00:48 you can do the same with any variable, but use with caution Dec 02 12:01:21 <_qwerty_> bluelightning:yes I understand Dec 02 12:09:52 bluelightning: so some of the python modules are installed because there are some other applications that require them? So if packages are split, does the package foo-meta get created so it is possible to install the full package? Dec 02 12:10:03 bluelightning: thanks a lot by the way. Really learned a lot from you Dec 02 12:14:41 chankit: I'm afraid we are not consistent, it depends on the recipe... though a lot of them make the main package depend upon all other packages (and to be honest that's what gstreamer plugins recipes should be doing, there is a bug open to fix that) Dec 02 12:14:43 chankit: no problem Dec 02 12:15:54 bluelightning: I understand that it has a lot to do with the cook but it's hard for me to see the way the packages are created? Dec 02 12:16:00 ignore the ? mark Dec 02 12:16:32 for python, i read the recipes and I have no idea that python-modules is there Dec 02 12:16:57 bluelightning: may I see the bug report? Dec 02 12:19:21 rburton: I am testing uboot class Dec 02 12:19:35 chankit: https://bugzilla.yoctoproject.org/show_bug.cgi?id=5589 Dec 02 12:19:36 Bug 5589: normal, Medium, 1.6.2, cristian.iorga, ACCEPTED , gst-plugins-* main package itself is useless Dec 02 12:20:16 chankit: we do have the Toaster tool that allows you to inspect build output including packages Dec 02 12:20:19 otavio: thanks Dec 02 12:20:37 chankit: you can also have a look at the packages produced by a recipe just by looking under packages-split under the workdir for the recipe Dec 02 12:28:20 bluelightning: yocti : thanks Dec 02 12:30:06 bluelightning: i read about toaster and it looks like it's gonna be hob replacement. Is it just hob with web interface then? Dec 02 12:31:08 bluelightning: btw, hob should be able to show the list of all packages shouldn't it? Dec 02 12:35:40 chankit: yes, toaster will completely replace hob in a future release, at the moment it doesn't have image customisation capabilities (and in the last stable release there is no support for building, only inspecting the build output) Dec 02 12:36:21 chankit: yes hob should be able to show that as well, though you can't see the packages per recipe Dec 02 12:38:57 bluelightning: ah i see..I guess that explains why I didn't see things like python-module and gst-plugins-meta then Dec 02 12:47:11 rburton: I found two issues Dec 02 13:24:23 hello ! - if I have two recipe with the same name source/meta-glsdk/recipe-bsd/u-boot-glsdk.bb and source/meta-ti/recipe-bsd/u-boot-glsdk.bb Dec 02 13:24:51 how can I tell bitbake to specifically build the first one (because it always rebuild the second one when I specify "u-boot-glsdk" Dec 02 13:24:55 thanks Dec 02 13:31:37 Hi acidfu, you can do it by changing the priority in conf/layer.conf Dec 02 13:31:42 in meta-glsdk Dec 02 13:31:46 acidfu: which one gets picked in this case will be determined by the layer priorities between meta-glsdk and meta-ti (higher number wins) Dec 02 13:31:59 ok Ill look at this configuration file Dec 02 13:33:08 strange because meta-glsdk/conf/layer.conf number is higher (BBFILE_PRIORITY_meta-glsdk = "15") vs (BBFILE_PRIORITY_meta-ti = "6") Dec 02 14:10:25 acidfu: that is odd... what do you get if you run: bitbake-layers show-recipes u-boot-glsdk Dec 02 14:16:34 Hi all, I try to include fsck.ext2/3/4 to my linux image. So I added e2fsprogs to my image's packages list and it does not works. I have binaries in "tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/e2fsprogs" folder but not in my linux image. Dec 02 14:16:56 Does anybody knows the solution to resolve this problem ? Dec 02 14:17:39 dcyrille18: the e2fsprogs package is split up into a number of sub-packages Dec 02 14:19:32 Ok, so you think I must include "e2fsprogs-e2fsck" in my packages list ? Dec 02 14:20:27 dcyrille18: right yes I was just about to say that Dec 02 14:21:53 Lol, ok, I'm trying that. Thank you for your help bluelightning. Dec 02 14:23:23 hello guys Dec 02 14:24:04 I think I'm getting older. Trying simple thing 'BBLAYERS+="/some/stuff" bitbake -e | grep BBLAYERS' shows that variable does not get appended Dec 02 14:24:08 any reason for that? Dec 02 14:24:27 did exactly same thing with some other BB_* variable, worked no problem Dec 02 14:24:43 well, actually I tried few variations Dec 02 14:24:57 like 'BBLAYERS="$BBLAYERS /some/stuff"' Dec 02 14:25:08 or 'BBLAYERS_append=" /some/stuff"' Dec 02 14:27:21 dcyrille18: are you telling, that you did 'IMAGE_INSTALL += "e2fsprogs"' on the image recipe and running board says 'e2fsprogs' is not installed? Dec 02 14:28:05 dcyrille18: bad luck :\ Dec 02 14:33:30 Xz: not all variables are allowed through from the external environment; even if the variable is, if it's then set with = in the configuration that'll override whatever was in the environment Dec 02 14:37:47 bluelightning: so you are telling me I am not allowed to overwrite BBLAYERS (and BBPATH as well) on command line? Dec 02 14:45:30 bluelightning: BBLAYERS by default assigns with '?=' in bblayers.conf Dec 02 14:50:42 Xz: not by default, no, we are selective about the variables we allow through from the external environment Dec 02 14:50:57 Xz: you are free to extend that selection using e.g. BB_ENV_EXTRAWHITE Dec 02 15:12:09 I have a difficulty to compile gstreamer-plugins-bad : http://pastebin.com/F7vXhJEV Dec 02 15:15:02 "arm-poky-linux-gnueabi-gcc: error: unrecognized argument in option '-march=x86-64'" Dec 02 15:15:12 an arm compiler is being asked to compile x86 code Dec 02 15:16:19 rburton1: yes, I understand the error, but who could do that ? I changed from daisy to dizzy and I didn't have this error before Dec 02 15:17:08 s/who/what Dec 02 15:17:25 jmleo: works for me. does your layer have any patches for it? Dec 02 15:17:51 rburton1: I will check, is there a fast way to check this ? Dec 02 15:18:15 you look at your layers for gst-plugins-bad recipes and appends Dec 02 15:18:34 yes, but can bitbake list all recipes and appends ? Dec 02 15:19:38 jmleo: erm, bitbake-layers i think can. the big question is why did the configure script think that its running on osx and so enabled the cocoa support Dec 02 15:19:45 hi, I'm looking for a way to include build configuration information in my built image. The "Build Configuration" info that prints out when I invoke my bitbake command would be good, or the metadata-revs file from the buildhistory (but I think that might be difficult since it doesn't seem to be written until after the image has been created) Dec 02 15:20:06 Is the "Build Configuration" text accessible from within yocto? Dec 02 15:22:05 jmleo: you want to look at the configure output to see why it wants to build the cocoa backend i guess Dec 02 15:22:29 hm, maybe it found gnustep on the host? Dec 02 15:22:36 jmleo: do you run windowmaker or something like that? Dec 02 15:24:28 I run urxvt Dec 02 15:24:36 knewb: yes... in fact a patch was sent to implement this very thing Dec 02 15:25:18 bluelightning: really?! do you have any pointers to that patch? Dec 02 15:25:19 jmleo: pastebin the configure log output, that's probably the most helpful thing Dec 02 15:26:33 rburton: I will, but right now I am trying with a cleanall og the package and I compile it in xterm Dec 02 15:26:57 jmleo: the host terminal won't make a difference. i'm wondering if you've got gnustep libraries installed in your image or build machine Dec 02 15:27:08 knewb: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ed3e25379c22da57a829f323b9404dd240de2272 Dec 02 15:30:42 rburton: here is the configure : http://pastebin.com/wgaQUGhn Dec 02 15:32:09 checking for gnustep-config... /usr/bin/gnustep-config Dec 02 15:32:10 checking for GNUstep... yes Dec 02 15:32:13 so yes, you've got gnustep installed Dec 02 15:32:30 and the gstreamer build system is broken Dec 02 15:32:32 bluelightning: awesome, thank you Dec 02 15:34:18 jmleo: add —disable-cocoa to EXTRA_OECONF for that recipe Dec 02 15:39:01 ndec: thanks for testing that x/mesa series! Dec 02 15:39:27 rburton: np. i was quite happy to see it today! Dec 02 15:50:16 Hey guys, i'm new to yocto and i'm having some issue : I'm trying to build on pandaboard and my local.conf line is something like this (amongst other lines) ... MACHINE ??= "pandaboard" ... but i'm getting an error that basically says that the machine name is incorrect : .... Please set a valid MACHINE in your local.conf or environment .... Dec 02 15:50:45 you have a layer that defiens the pandaborad machine Dec 02 15:51:03 yes the meta-ti Dec 02 15:52:08 dpavel: in bbalyers.conf too? Dec 02 15:53:18 this is my bblayres.conf Dec 02 15:53:43 LCONF_VERSION = "6" Dec 02 15:53:44 4 Dec 02 15:53:44 5 BBPATH = "${TOPDIR}" Dec 02 15:53:44 6 BBFILES ?= "" Dec 02 15:53:44 7 Dec 02 15:53:44 8 BBLAYERS ?= " \ Dec 02 15:53:46 9 /home/daniel/Karanka/yocto/poky/meta \ Dec 02 15:53:48 10 /home/daniel/Karanka/yocto/poky/meta-yocto \ Dec 02 15:53:50 11 /home/daniel/Karanka/yocto/poky/meta-yocto-bsp \ Dec 02 15:53:52 12 " Dec 02 15:53:54 13 BBLAYERS_NON_REMOVABLE ?= " \ Dec 02 15:53:56 14 /home/daniel/Karanka/yocto/poky/meta \ Dec 02 15:53:58 15 /home/daniel/Karanka/yocto/poky/meta-yocto \ Dec 02 15:54:00 16 /home/daniel/Karanka/yocto/poky/meta-ti \ Dec 02 15:54:02 dpavel: heard of pastebin? Dec 02 15:54:02 17 " Dec 02 15:54:04 ~ Dec 02 15:54:14 ye, sorry Dec 02 15:54:17 dpavel: put it in BBLAYERS Dec 02 15:54:33 (NON_REMOVABLE is basically metadata and i'm not sure why we put it in that file) Dec 02 15:55:46 YPTM: armin is on Dec 02 15:56:09 you're eager! Dec 02 15:59:18 rburton: got it, it works now, thank you. Dec 02 15:59:51 YPTM: joined Dec 02 16:00:23 YPTM: Sona joined Dec 02 16:00:34 rburton: well we already have xmas setup Dec 02 16:00:58 YPTM: Joe MacDonald on. Dec 02 16:01:32 YPTM: Matthew on Dec 02 16:03:38 YPTM: I have hold music. Dec 02 16:03:49 rburton: adding disable-cocoa to EXTRA_OECONF is working Dec 02 16:03:50 YPTM: joined Dec 02 16:03:50 halstead: Glad it's not just me. :-) Dec 02 16:03:59 YPTM: Belen joined Dec 02 16:04:01 YPTM: Josep joined Dec 02 16:04:09 YPTM: Saul is here Dec 02 16:04:15 YPTM: Ready-Access Number: 8007302996 Access Code: 2705751 Dec 02 16:04:16 jmleo: can you send a patch with that please? the detection and build is clearly broken Dec 02 16:04:32 YPTM: Stephen Joined Dec 02 16:04:38 YPTM: Tom Z here Dec 02 16:04:44 * RP joined Dec 02 16:04:45 YPTM: Denys is dialing in Dec 02 16:05:26 YPTM: ross here Dec 02 16:05:26 sjolley: sorry, you may not remember my nick. Sean Hudson from MGC Dec 02 16:05:35 rburton: well, this would probably be better to use a PACKAGECONFIG[cocoa] ? Dec 02 16:05:38 YPTM: not able to join as I have a conflict... sorry Dec 02 16:05:42 YPTM: AlexG on call Dec 02 16:06:14 bluelightning: hehehe, I'm skipping an OPS meeting since I haven't made one of these in a while Dec 02 16:06:14 YPTM: current 1.5 qa status: https://wiki.yoctoproject.org/wiki/1.5_QA_Status Dec 02 16:06:17 YPTM: did I miss my name, Matthew? Dec 02 16:06:28 Hi, what could be wrong in 1.5.3 when meta package DEPENDS on meta packages which create SDK etc, but populate_sdk seems not to get called through the meta packages, and tmp/deploy doesn't have an sdk. Using sstate cache. Dec 02 16:06:58 mcweigel: You did, I'm pretty sure sjolley recorded you. Dec 02 16:07:20 mcfrisk: DEPENDS might not be the right thing there... you probably want do_build[depends] = "otherrecipe:do_populate_sdk" Dec 02 16:07:59 k Dec 02 16:08:01 I got Matthew. Thank Dec 02 16:08:35 mcfrisk: DEPENDS translates to do_configure of the recipe in which it is specified depending on do_populate_sysroot of what's mentioned in DEPENDS Dec 02 16:09:33 * fray isn't able to make the meeting today.. I'm stuck at the Jeep dealership.. :P Dec 02 16:10:50 fray: just buy a new one! Dec 02 16:11:02 bluelightning: meta package which just DEPENDS on other meta packages and groups works with 1.6. Dec 02 16:11:18 I'm sure they would like that.. ;) Dec 02 16:11:41 mcfrisk: if by meta you mean it inherits meta, then yes it should work Dec 02 16:12:05 mcfrisk: DEPENDS should work in that situation, I mean Dec 02 16:17:04 bluelightning: hmm, seems like I was missing 'inherit meta', now bitbake meta-pkg is doing alot more... Dec 02 16:17:45 sjolley, Open: extended downtime Dec 02 16:21:39 halstead: appreciate the headsup thanks Dec 02 16:21:53 :) Dec 02 16:21:57 halstead: I missed. when is the planned outage? Dec 02 16:22:54 darknighte, I'm planning 2 to 4 hours during this Friday in the afternoon. Pacific timezone. Dec 02 16:23:07 Posting to yocto-infrastructure. Dec 02 16:23:53 cvechecker Dec 02 16:24:08 halstead: thx Dec 02 16:26:08 bluelightning: indeed, 'inherit meta' fixed the sdk deployments, thanks! Dec 02 16:26:53 rburton: done, little patch Dec 02 16:28:10 I have another issue with hostapd... Dec 02 16:28:12 http://pastebin.com/93vhZ23T Dec 02 16:28:34 it is using a /usr/lib ! Dec 02 16:34:28 jmleo: thanks Dec 02 16:34:53 jmleo: try bitbake whatever it is that provides libnl3 first Dec 02 16:35:12 jmleo: (this is why i do builds on a machine with minimal development headers on) Dec 02 16:37:03 rburton: so, hostpad needs a DEPENDS on whatever provides libnl3... ? :) Dec 02 16:37:49 it is recipe libnl Dec 02 16:38:12 and in hostapd there is "DEPENDS = "libnl openssl" Dec 02 16:52:45 rburton: libnl3 is installed and I even tried to add a REPENDS on libnl but still have the same issue Dec 02 17:07:05 jmleo: sounds like hostapd decides to look at the host first… easy fix would be to remove that header package from your host Dec 02 18:03:10 I was building an out-of-tree kernel module... and having KERNEL_VERSION set in the environment caused problems for me. Dec 02 18:03:23 I think it was conflicting with the KERNEL_VERSION macro in include/linux/version.h Dec 02 18:03:28 Anybody else ever run in to this? Dec 02 19:19:36 does anyone know if systemd is part of the yocto qa tests Dec 02 19:20:33 if not, spnsors welcome :0 Dec 02 19:48:27 halstead: are you moving machines currently? Bugzilla seems to be down Dec 02 19:52:34 halstead: nm seems to be a local issue :-( Dec 02 19:53:57 armpit: you can look at the bugzilla.yoctoproject.org testopia area, a quick search shows 6 tests, so not extensive systemd testing at this time, more are welcome! Dec 02 20:09:20 hmm, is it true wic need rm_work removed? Dec 02 20:16:38 Crofton|work: last time i used it (whcih was a long time ago), yes it grabbed the rootfs directory from work instead of unpacking the deploy tarballs. Dec 02 20:16:49 Crofton|work: remember you can disable rm_work per-recipe :) Dec 02 20:17:14 remind me how Dec 02 20:18:25 RM_WORK_EXCLUDE Dec 02 20:18:26 RM_WORK_EXCLUDE = "list of recipes" iirc Dec 02 20:18:51 hmm Dec 02 20:19:05 hm that logic isn't good Dec 02 20:19:05 from local.conf, not the recipe ? Dec 02 20:19:25 hm you can probably set it in the recipe Dec 02 20:19:34 as the rm_work task happens in the recipe's scope Dec 02 20:20:17 the class says do it in local.conf Dec 02 21:01:35 I thought we had a recentish checkin to make pseudo stop falling back to host passwd. But I've been sick (and still am) and may have forgotten things. Dec 02 21:33:23 seebs: it was in master only Dec 02 21:34:24 hm i wonder if it was a re-stage of base-passwd and the old sysroot passwd didn't have a root entry Dec 02 21:34:45 seebs: did pseudo look for the specific user in every passwd file it finds? Dec 02 21:34:56 Is there any way for a bbclass or layer or bb to provide a value for ASSUME_PROVIDED? Dec 02 21:35:09 so if the sysroot passwd was missing root, it would still try the host? Dec 02 21:35:19 fishey: the layer.conf can add to it, yes Dec 02 21:35:34 rburton: thanks Dec 02 21:51:08 Is there a decent way to append something to ASSUME_PROVIDED unless a user specifically requests it not to be appended? Right now I'm planning on making a variable with a default value of the PNs to be appeneded to ASSUME_PROVIDED, and recommending the user override that variable (in local.conf or otherwise) to be empty if they don't want it to be assumed. Dec 02 21:55:02 that's one way Dec 02 21:55:19 another is to have a local.conf.sample that your distro uses and that sets assume_provided Dec 02 21:55:30 that's what poky does for the assume-provided of libsdl-native Dec 02 21:55:45 don't want it, delete it from your local.conf Dec 02 22:10:14 sgw_ Sorry I missed your ping. I'm rebuilding firewalls but nothing should be interrupted by it. Dec 02 22:33:56 anyone working for TI ? :P I'm wondering why their GLSDK is partly based on yocto, ans partly based on shell script and Makefile Dec 02 22:34:09 why not just yocto Dec 02 22:38:56 is there anyone who can point me in the direction of a mercurial recipe? I only seem to be able to find mercurial-native Dec 02 23:05:52 ajtag: I'm not aware of one... it would be ideal to convert the mercurial-native recipe over to a target recipe + BBCLASSEXTEND = "native" Dec 02 23:06:56 bluelightning, thanks. I am having a go at just writing the plain one now Dec 02 23:27:54 rburton: my layer doesn't include a distro, and also doesn't provide a local.conf.sample at the moment, so I'll probably stick with my slightly obtuse method. Dec 03 02:13:49 anyone can help with gstreamer1.0 plugins? **** ENDING LOGGING AT Wed Dec 03 02:59:58 2014