Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - mkbrown69

Pages: 1 ... 6 7 [8] 9 10 ... 13
Users / Re: LinuxMCE community, lets talk.
« on: November 14, 2012, 04:02:07 am »
sad face. all i can say. bums me out to hear that we are basically suffering because of software we dont maintain. awesome :|

The problem with MythTV in LMCE is that it's 0.23, and that version had known stability issues.  When I had upgraded my (non-LMCE) MythTV, it was considerably more stable on 0.24 and 0.25 than it ever was on 0.23.  If we could upgrade the LMCE MythTV parts to support 0.25-fixes, that would likely address some people's stability issues.  0.26 introduces UTC time in the database, so the Level of effort there might be a bit higher at this point in time.  Besides, it's never a good idea to upgrade to a point zero release on any software... Let it get to 0.26.2 before considering it for inclusion when stability is key.

My $0.02 worth before HST.



Users / Firewall issues
« on: November 12, 2012, 04:27:36 am »
Good day folks!

I'm having some issues with the stock firewall settings (I added the "domain" TCP/UDP 53 ones via the LMCE firewall page to play with it).  Lots of packet denied messages, including localhost.

Code: [Select]
[1062546.521689] IPv4 packet denied: IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC= DST= LEN=57 TOS=0x00 PREC=0x00 TTL=64 ID=39621 DF PROTO=TCP SPT=47142 DPT=3450 WINDOW=770 RES=0x00 ACK PSH URGP=0

[1062570.285733] IPv4 packet denied: IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:52:54:00:a8:7f:eb:08:00 SRC= DST= LEN=68 TOS=0x00 PREC=0x00 TTL=128 ID=14050 PROTO=UDP SPT=52330 DPT=52330 LEN=48

[1062522.277283] IPv4 packet denied: IN=eth1 OUT= MAC=54:52:00:6a:5b:4b:00:0c:29:b5:fd:73:08:00 SRC= DST= LEN=136 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=703 DPT=2049 LEN=116

Interfaces are correct, eth0 is outside, eth1 is inside (LMCE network).

Code: [Select]
# iptables -L
Chain INPUT (policy DROP)
target     prot opt source               destination
LOG        all  --  anywhere             anywhere            limit: avg 5/min burst
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere            state RELATED,ESTABLISH
ACCEPT     all  --  anywhere             anywhere            mark match 0x1
ACCEPT     udp  --  anywhere             anywhere            udp dpt:bootps
ACCEPT     all  --      anywhere
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:https
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:www
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:domain
ACCEPT     udp  --  anywhere             anywhere            udp dpt:domain

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Any ideas why localhost and the internal network are denying so many packets?

Code: [Select]
dcerouter_1021496:/var/log# cat syslog | grep "IPv4 packet denied" |wc -l
dcerouter_1021496:/var/log# cat syslog | grep "IPv4 packet denied" |grep |wc -l
dcerouter_1021496:/var/log# cat syslog | grep "IPv4 packet denied" |grep 192.168.80 |wc -l

Thanks for your time!


P.S.  disabling the firewall via the web admin doesn't actually disable or clear the firewall.   I had to clear with iptables -F and iptables -Z.

Users / Question about sambahelper user.
« on: November 05, 2012, 03:37:33 am »
Good day folks!

I've got a question about the sambahelper user.  Obviously, it's used on the core and on the MD's.  It's being assigned UID's in the "normal" unix user range, which can conflict with existing core and NIS users.  As you see below, it's inconsistent between what was created on moon72 and what was created on the core.

Code: [Select]
root@moon72:~# cat /etc/passwd | grep samba
sambahelper:x:1000:1000:Pluto Samba Share Helper:/tmp:/bin/false

root@moon72:~# ypcat passwd
mkbrown:x:1000:1000:Michael Brown,,,:/home/mkbrown:/bin/bash
sambahelper:x:1001:1001:Pluto Samba Share Helper:/tmp:/bin/false

The sambahelper user is created in PlutoStorageDevices/ It is created using the following code starting on lines 31

Code: [Select]
## Samba Share Helper
if [[ "$(id -u sambahelper)" == "" ]] ;then
        useradd -c "Pluto Samba Share Helper" -d /tmp -s /bin/false sambahelper

Wouldn't it be better to have it created as a "system" user using -r, or to statically assign something like -u 999 -g 999 ?

I'm throwing this out there for someone much more knowledgeable about this subsystem to educate me, or suggest I file a Trac ticket.

Thanks for your time!


Feature requests & roadmap / Re: Status / overview page?
« on: November 01, 2012, 02:59:03 pm »
some progress...
some graphs showing up now ... with zoom function...
i'll need to find a smart way to filter data and add a timeframe selector.

Looks good!  Spelling mistake for "usage" though...


Users / Re: Disk size incorrect / disk full?
« on: October 29, 2012, 06:04:20 pm »
I've done this for all folder (except /mnt/), and the total shouldn't be over the 25GB.
Or am i doing something wrong?
sudo du -h /foldername


One option is
Code: [Select]
sudo du -hxs /
And wait patiently... That will summarize everything under / that is on the same file-system as a total size (i.e. not mounted from a different disk, or the tmpfs filesystems).  x keeps it on the / file-system, and s gives you the summary, rather than each file or directory listed.

/home/camera (or cameras; going from memory here) will have videos and such of motion events, those can consume a lot of space.

If you want to find your largest files, try the following:

Code: [Select]
sudo du -ahx / | sort -h -r -o /tmp/largefiles.txt  && head -10 /tmp/largefiles.txt  

will net you your top 10 space hogs...



Feature requests & roadmap / Re: News flash
« on: September 05, 2012, 06:38:53 pm »
Just a thought...  It could be implemented as a re-usable component, like a Twitter/XMPP/RSS feed reader...


Developers / OT: climate plugin for local weather
« on: August 30, 2012, 03:07:25 pm »
I have played with the climate plugin to pull local airport weather (based on a wiki article, thank you to that author)

I'm interested in doing something like that too... Misterhouse has a "weather hash", and various scripts & plugins that will populate the weather hash (temperature, humidity, rain fall, wind speed, etc) to allow for automation to take action based on weather conditions.  Could you put up the link to the wiki article, and maybe describe how you're using it?



Installation issues / Re: [SOLVED] IP Camera in 1004
« on: August 21, 2012, 07:28:43 pm »
I need to thank you.
For the support, and the extra lessons...

I learned:
  • How to raise the loglevel (/etc/pluto.conf > 4,6,8,10)
  • Each device has his own log file (/var/log/pluto), based on the id
  • With the id. you can find a lot more in the global logfile (/var/log/pluto/DCErouter.log).
  • And that it isn't so difficult to create a template as it seems. ;)

I'd like to echo brononius, and say thanks as well.  I've been following this thread as I'm about to get my cameras configured (playing with the 2121 template, but will look at doing a DCS-930L soon - unless Armor Gnome beats me to it) after I finish something else I've been working on.  I'm guessing it's probably a bad thing to try to do a sql-cvs diff when working on multiple un-finished templates.

It's been very informative watching this thread progress.  Thanks for educating a few of us in the process.



Users / Re: Requesting Help (small wiring project)
« on: August 21, 2012, 07:19:59 pm »
There is a small cap between +'ve and gnd.  A few more caps around the usb connectors.
The caps will be important, as those are for DC power conditioning and noise suppression, so Armor Gnome will need to match those values in his build.  You could always post a pic of the parts if they're surface mount, and we could figure out the values for him.

Armor Gnome,

Make sure your ground pins are longer than your power pins.  For 'hot insertion' you always want ground to make first, and break last to prevent damage to your electronics.


(former telecom R & D lab technician)

Feature requests & roadmap / Re: Bloated MDs
« on: August 17, 2012, 07:31:20 pm »
Good day folks!

Having been thinking about this for quite some time (but not having the full understanding of the LMCE architecture to implement it) I think both camps could be satisfied with the concept of 'roles' for net-booted devices.  My thoughts were along the lines of:

  • MD
  • Workstation (or laptop)
  • Workstation w/MD
  • Workstation w/orbiter

Imagine this: when a device is net-booted for the first time, the wizard asks what role this machine will be fulfilling (with some helpful text around it explaining what each does).  Then, the applicable software packages are applied onto the base OS to full-fill the role.  We're implementing a similar approach at work for server builds, using Puppet, which is a configuration and compliance management tool.  It uses a component called Facter to determine facts about a client system (like architecture, virtual, OS Family/release, etc.) which can be used to take actions based on the facts it discovers about the system.  It can be used to configure software packages, user and service accounts, install or remove software, change system parameters (like sysctl), etc.  And, there's a nice community of pre-built modules, plus stuff on github, or  you can write your own (including facts you wish to discover, then act on).  

It's a powerful configuration framework which I think would be a good fit for LinuxMCE.  It would be a radical change in how LMCE works under-the-hood, and I think it would make future upgrades and life-cycle management activities a lot easier, as you can specify different things based on custom facts or facts like the OS version or hardware architecture.  Think Pi MD vs an x86 MD.  You can have the same role applied to both, but satisfy the architecture specific dependencies and configuration using the same toolset and policy.  You can also use it to manage the core and it's services.  There are implementations on the web where folks are using Puppet to build the PuppetMaster server, which is then used to build client systems (allowing them to bootstrap an entire environment, lets say in a disaster scenario).

Puppet is something that can be implemented incrementally, when each change you want to make is quantified, so it represents a low risk to stability.  Start with the easy and non-intrusive stuff first, and as the implementation matures, go for the more intrusive changes one-by-one.  That's the approach we're taking with 3 *nix OS Families, 4 hardware architectures, 4 hypervisors, and 10 OS variants in production.  I thought I'd throw this option out for discussion, since there's a lot of interest in making the MD's (and other PC's) fit-for-purpose.  Feel free to browse the links above, google it, or 'apt-cache show puppet puppetmaster facter' from your core.

Hope this provides some food for thought!  Thanks for your time!


Installation issues / Re: 10.04 DVD install experience
« on: August 17, 2012, 06:13:13 pm »
For the second part of my post,... I was actually thinking VM Core and VM MDs on the same physical machine isolated by the lack of bridging to the network...


Assuming your virtual core's eth0 is on the internet, and eth1 is on the LMCE network, you can do a host-only network for the virtual core and virtual MD to communicate on.  So, the vCore eth0 would have it's interface attached to the bridge your host's internet-facing interface is on, and the vCore eth1 would be attached to a bridge which is not bridged to physical ports.  The vMD would have it's eth0 attached to the same virtual bridge.  See <> under private virtual bridge, or see if your version of virt-manager supports configuring host-only networks <>.  

As far as graphics goes, you may have better luck with the cirrus driver, or with the VMware vga driver (vmvga or svga, depending on your qemu version).  The VMware VGA driver ships with most current Xorg packages.  Some of the devs run ESX, so someone may have coded in support for it's video drivers.

Hope that helps!


Users / Re: LMCE as DNS Server?
« on: August 13, 2012, 04:05:21 am »
Speaking as a *nix sysadmin who works on many Linux variants, plus Solaris, HP-UX, and AIX, I can tell you for a fact that a system's local DNS config file is /etc/resolv.conf (without an ending 'e').

If you want to find out what's supposed to be in that file as far as config options go, try 'man resolv.conf' from the command line.  You can use the 'nslookup' command to test your DNS config (man nslookup to see how to use it).



Do you know of an easy way to detect the frame rate of a specific file?

Mediainfo.  # apt-get install mediainfo

       MediaInfo supplies technical and tag information about a video or audio

       What information can I get from MediaInfo?

       - General: title, author, director, album, track number, date, duration...
       - Video: codec, aspect, fps, bitrate...
       - Audio: codec, sample rate, channels, language, bitrate...
       - Text: language of subtitle
       - Chapters: number of chapters, list of chapters

       What format does MediaInfo support?

       - Video: MKV, OGM, AVI, DivX, WMV, QuickTime, Real, MPEG-1, MPEG-2, MPEG-4, DVD (VOB)...
       - Video Codecs: DivX, XviD, MSMPEG4, ASP, H.264, AVC...
       - Audio: OGG, MP3, WAV, RA, AC3, DTS, AAC, M4A, AU, AIFF...
       - Subtitles: SRT, SSA, ASS, SAMI...

       What can I do with it?

       - Read many video and audio file formats
       - View information in different formats (text, sheet, tree, HTML...)
       - Customise these viewing formats
       - Export information as text, CSV, HTML...
       - Graphical Interface, Command Line, or library versions available

   Display information about a video file
        $ mediainfo foo.mkv

   Display aspect ratio
        $ mediainfo --Inform="Video;%DisplayAspectRatio%" foo.mkv
        $ mediainfo --Inform="Video;file://Video.txt" foo.mkv

       Both forms are equivalent if Video.txt contains:

   Display aspect ration and audio format
        $ mediainfo --Inform="file://Text.txt foo.mkv

       If Text.txt contains:

       - "Video;%DisplayAspectRatio%"
           Then the display aspect ratio is printed out.

       - "Audio;%Format%"
           Then the audio format is printed out.



Installation issues / Re: system freeze
« on: July 10, 2012, 03:43:46 am »
I've had errors like those, including the hard resetting link when one my raid 1 sets was doing it's weekly checks.  Occasionally, it would become totally unresponsive, requiring a power down of the system in order to restore it, and then I'd have to re-add it to the array and re-sync.  It's happened a few times (and only under heavy load), and I was close to RMA'ing the drive.  Then, this past Sunday morning I found my server off, and unable to power it back up.  The power supply had quit (and probably been on it's way out for a while due to capacitor aging), and was likely browning out under load.  So it's possible your power supply is on it's way out, or it's under-powered for the load.

There's a good power supply calculator at

Try entering everything you have, and see what the recommended size is.  You can also add 30% for capacitor aging if your power supply is over a year old.  You'll be surprised how much it changes when you factor that in.

Hope that helps!


Users / Re: Newbie camera question
« on: July 09, 2012, 06:49:06 pm »
Glad you're still fiddling with kmotion, Mike. What, apart from the RAM disk buffering, does kmotion bring to the party? I had initially assumed it was just a graphical wrapper for motion and would not add functionality beyond visualisation.


Kmotion2 brings a few things (as a stand-alone package), but not all apply in the LMCE context.  Some of those features can be replicated with existing LMCE features.  So, I was looking to try and understand both, rather than just bolting on Kmotion2 and incurring the wrath of Thom. ;)

  • Fire off scripts (like e-mails w/picture attachments) when motion events occur (some functions could be done with LMCE events)
  • Ability to configure motion masks in the Web GUI (doesn't presently exist in LMCE)
  • A timeline view on a per-camera basis (I'm still trying to understand LMCE and it's alerts view)
  • Selectable multi-camera views, single , pairs, quads, up to 16 cameras
  • Motion conf file configuration using a web GUI ('motion wrapper' and individual devices in LMCE)
  • motion executable service management (done with motion wrapper and/or OS init scripts in LMCE)
  • RAM-disk based processing, for multi-camera performance improvements

The big ones for me were the Mask configuration (mask off areas that you don't want triggering motion events), the firing off of scripts/e-mails/events, and the camera views.  I'm going to back-burner this project until I get the CM-19a 'mochad' driver done, and look at what the Advanced IP Camera template will do for me...  Too many projects on the go right now...



Pages: 1 ... 6 7 [8] 9 10 ... 13