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 ... 9 10 [11] 12 13
Users / Re: 'Blank' passwords
« on: February 23, 2012, 05:59:45 pm »

Look into the package dbconfig-common. It's the means for creating database users in a manageable way using package mechanisms.

From the apt description...

Description: common framework for packaging database applications This package presents a policy and implementation for  managing various databases used by applications included in Debian packages.
 It can:
  - support MySQL, PostgreSQL, and sqlite based applications;
  - create or remove databases and database users;
  - access local or remote databases;
  - upgrade/modify databases when upstream changes database structure;
  - generate config files in many formats with the database info;
  - import configs from packages previously managing databases on their own;
  - prompt users with a set of normalized, pre-translated questions;
  - handle failures gracefully, with an option to retry;
  - do all the hard work automatically;
  - work for package maintainers with little effort on their part;
  - work for local admins with little effort on their part;
  - comply with an agreed upon set of standards for behavior;
  - do absolutely nothing if that is the whim of the local admin;
  - perform all operations from within the standard flow of package management (no additional skill is required of the local admin).

That's probably the best way forward.  It's what Debian and MythBuntu uses for MythTV/MySQL database management.  I too would like to see the security on the DB users tightened up, but I'm busy with a z/OS course for work which is eating up my spare time...

Hope that helps!


Installation issues / Re: Core as a VM on a mac OSX server
« on: February 15, 2012, 06:20:02 pm »

While I'm not "WhateverFits", I would recommend NOT using VMWare player.  Because it sits on top of an existing OS, there's a lot of overhead involved in trying to run LMCE that way.  ESXi would be a better fit, as it's a bare-metal hypervisor (a Type 1 hypervisor).  Much less overhead involved.

Personally, I'm running an existing Linux Server as a KVM virtual host.  I have two NICs on the physical box, bridged to separate physical and virtualized networks.  I have a br_ext, which is my existing production environment, and a br_int, which is the LMCE .80.0/24 network.  My LMCE test instance is a virtual with 2vCPU's and 1.7G of RAM.  LMCE owns the internal network on it's virtual eth1, bridged to br_int, and it is dual-homed (meaning that eth0 in LMCE is attached to br_ext, connected to my WAN router and the rest of world).  I have a wireless router on the external net, and a separate one on the internal net, letting me flip between the existing non-LMCE production network and my LMCE testing network.  As I complete some migration and Proof-of-concept activities, I'm then migrating services into the LMCE environment while not affecting my existing prod environment.  When I'm fully ready, I'll be able to cut-over to LMCE as the production environment with minimal downtime, as all the backend stuff will have been completed.  It's not at all obvious that I'm a SysAdmin by day, eh?   ;)

Hopefully this gives you some food for thought.


Plus, the only system that I DO have with an nVidia card can't work with my Hauppauge cards (1600s), due to a (known) hardware conflict.

I have nVidia working with 2 HVR-1600's.  You just need to change the vmalloc parameter in the kernel boot line.  Google "nvidia hvr-1600 boot vmalloc" or look at and

I'd set mine to 256M.



Users / Re: 1wire support
« on: February 07, 2012, 10:33:12 pm »

To check for it from command-line, on the core issue

dpkg --get-selections | grep libowfs

If you get nothing from that, issue

sudo apt-get install libowfs27



Users / Re: Insteon 2412U
« on: February 03, 2012, 06:36:16 pm »
From what I can tell scenes are setup directly through LinuxMCE. It takes the place of the insteon software. So scenes will be defined within the web interface of LinuxMCE.


I'm more familiar with using Insteon via Misterhouse, as that's my present production environment.  With Insteon, you can have on device scenes, where multiple devices are linked and the scene is executed with one command that is acted on by all devices simultaneously.  There were past comments on the LMCE forums that scenes for Insteon devices were simply LMCE sending individual commands to each device, which puts more traffic on the Insteon network in the case of complex scenes.  So, my inquiry was more along the lines of "is that still the case?"  I had seen comments about someone writing a C device driver, but nothing appeared in the forums or trac to that extent.

Having scene support in LMCE where the scenes are downloaded to the devices and then executed by a single command would ensure a faster response time, less traffic for the Insteon network, and would give a fail-safe capability in the case that the LMCE core was down, so that lighting works the same with or without automation (major WAF sticking point).

Not sure if you're aware of this little Insteon gem or not...

Thanks for the reply, and hope that helps!


Users / Re: Insteon 2412U
« on: February 03, 2012, 04:09:21 am »

Since you're appearantly familiar with the PLM code, could you tell me/us if it presently supports Insteon scenes?  If so, would it support creating a scene in LinuxMCE that gets pushed into the devices, or merely triggering a scene that already exists in the devices (e.g. Manually linked scenes)?



Users / Re: 1wire support
« on: January 23, 2012, 09:27:41 pm »

You're not alone ;-)

I've been wondering too, mostly because I'm looking to implement 1-wire, but on a remote host.  OWFS supports that, but it looks like the 2161 Template was done to configure owserver for a serial port adapter like a 9097U.  I've been wondering if I should create a new 1-wire template, or modify the 2161 to support the other methods.

Would someone more knowledgeable about the 1-wire template like to suggest a course of action for USB and remote 1-wire support?



Feature requests & roadmap / Re: Monitoring
« on: January 23, 2012, 02:07:40 am »

What I think Thom is getting at is that if you're going to champion Cacti integration, you'll have to extend Cacti a bit to send DCE events, so that DataLogger can record them, and the rest of LMCE can act on them.  So, instead of Cacti sending an e-mail or SMS when a threshold is exceeded, it would use MessageSend to emit an LMCE event which Datalogger would record, and that the system could act on if a scenario was defined.  Like so...

Power usage goes over 5kw, Cacti generates a MessageSend to LMCE, Datalogger records the threshold exceeded event, and an "excessive power use" scenario is triggered, which broadcasts a message to all orbitors, and a "chi-Ching" sound is played over all audio devices.

So, it means some work extending Cacti, some work extending Datalogger, and some work figuring out events.  Plus, doing all that in such a way that someone else can extend your work to graph other things (soil moisture readings, humidity, Squid proxy results for domains, etc).  It would also probably involve integrating Cacti's web GUI into the LMCE web GUI, and use LMCE defined users.

I agree with you that Cacti and rrd's are great for recording some types of data, like multiple temperature sensors.  Assuming OWFS as a sensing infrastructure, it samples by default every 10 seconds per sensor.  So, that works out to 8640 samples per sensor per day.  Over time, those samples can be averaged because the further away they are from the present, the less need there is for precision (which is what RRD's do).   Cacti is also great at dealing with all the noise that syslog can generate.  Same with other types of repetitively sampled data, where the need for precision becomes less important over time.

Where I think Datalogger integration could really shine is for correlating events from multiple subsystems into a "timeline of events".  It's the concept of federated data; one overseer of other more specialized reporting/monitoring systems. It could be useful for debugging complex scenerios (this motion event triggered that lighting event when this other condition existed) as well as for security auditing (think alarm system event log), telephony logging, MythTV events, etc.  It would be especially nice if the Datalogger events could be viewed from an orbitor.  What would be really cool is heuristics to mine the Datalogger for patterns.  Think a "vacation mode" which operates lights based on the inhabitants past behaviours.

Just my $0.02 CDN as someone who's presently dealing with Federating configuration and compliance management systems at work (in addition to other things).


Users / Re: Core Only with TV Tuner?
« on: January 14, 2012, 05:16:37 am »
Good day!

Someone more knowledgeable will correct me if I'm wrong, but disabling the MD/Orbitor on the core will only affect your ability to VIEW media on the core.  The tuners are managed by MythTV or VDR (whichever you chose to set up when you installed LinuxMCE) and will run as background services.  I'm more knowledgable about Myth, as that's my present "production" environment at home (I'm testing and doing some infrastructure proof-of-concepts on LMCE right now, so it's not "prod" yet).

My MythTV backend (which would be a LMCE core) runs headless, and has two dual-tuner PVR-1600's in it, and it can use the two PVR-150's that are installed in a slave backend/front-end in the family room.  Myth is really great for running a distributed system, and you can run any combination of backends and front ends as your situation may require.  Since LMCE leverages Myth, you inherit those capabilities.

Hope that helps!


Users / Re: Is sysklogd needed?
« on: January 14, 2012, 04:31:11 am »
Nice work brononi!

Are you using the MySQL backend for rsyslog, or is cacti just parsing the logs?  If you want to get fancy, you can enable remote syslog sending on your MD's, listening on the core, and then you can run a central syslog server on the core.  We do that at work for the security guys.  Linksys and OpenWRT routers (and a few others) support sending their syslog output to a syslog host, so you could incorporate that if you wanted...

Just an FYI, Ubuntu 10.04 and newer use rsyslog.  I think most modern distros have ditched ksyslogd for rsyslog.

You might want to put up a wiki page (even if it's on your own user page) so that others can follow in your footsteps and play around with it.  It might stir up the creative juices...

In my case, I've been running collectd on my KVM virtual host and in the guests, as it can hook into the stats provided by libvirt on the host, and I can also see what's happening inside the guest via the collectd daemon running there.  To keep the stats fresh and the system responsive, I put the RRD's on a 4 GB logical volume on an SSD (I do the same with my existing MythTV/MySQL production system, and the MySQL used by my LMCE 10.04 virtual core that I'm testing (/var/lib/mysql for each of them is it's own logical volume on the SSD on the host).  Keeps the databases performing nicely and the system responsive.  Your Cacti implementation looks interesting, as some have used Cacti as a front end for the RRD's provided by collectd.

Thanks, and Happy New Year!


Installation issues / Re: Phone line admin page is missing in 1004
« on: December 20, 2011, 10:07:27 pm »
OK, maybe not an asterisk problem. I tried to reinstall and watch things more closely. Looks like there were download errors. If someone could help me out with the --fix missing syntax then I could investigate further.

sudo apt-get update
sudo apt-get install --fix-missing

That should do it for you!


Users / Re: mythconverg_bac out of control
« on: December 20, 2011, 05:18:41 am »
Here's the permissions for the binaries in /usr/bin {stock 0.23}

-rwxr-xr-x 1 root root   34632 2010-04-23 22:04 mythavtest
-rwxr-xr-x 1 root root 1433788 2010-04-23 22:04 mythbackend
-rwxr-xr-x 1 root root  588276 2010-04-23 22:04 mythcommflag
-rwxr-xr-x 1 root root  359088 2010-04-23 22:04 mythfilldatabase
lrwxrwxrwx 1 root root      31 2011-10-07 21:46 mythfrontend -> ../share/mythtv/
-rwxr-xr-x 1 root root 2209232 2010-04-23 22:04 mythfrontend.real
-rwxr-xr-x 1 root root   38688 2010-04-23 22:04 mythjobqueue
-rwxr-xr-x 1 root root  227312 2010-04-23 22:04 mythlcdserver
-rwxr-xr-x 1 root root   84164 2010-04-23 22:04 mythreplex
-rwxr-xr-x 1 root root   83764 2010-04-23 22:04 mythshutdown
-rwxr-xr-x 1 root root  359576 2010-04-23 22:04 mythtranscode
-rwxr-xr-x 1 root root   18052 2010-04-23 22:04 mythtvosd
lrwxrwxrwx 1 root root      31 2011-10-07 21:42 mythtv-setup -> ../share/mythtv/
-rwxr-xr-x 1 root root  363528 2010-04-23 22:04 mythtv-setup.real
-rwxr-xr-x 1 root root  141736 2010-04-23 22:04 mythwelcome

And the running processes...

 ps -ef |grep myth
mythtv    1309  1308  0 Dec17 ?        00:01:13 /usr/bin/mythbackend --logfile /var/log/mythtv/mythbackend.log --user mythtv
mythtv    3414  7578  0 23:13 ?        00:00:00 sleep 1
mythtv    7577  1309  0 Dec18 ?        00:00:00 sh -c /usr/pluto/bin/  >>/var/log/mythtv/mythfilldatabase.log 2>&1
mythtv    7578  7577  0 Dec18 ?        00:10:34 /bin/bash /usr/pluto/bin/

And the permissions on /var/log/mythtv
drwxrwsr-x  2 mythtv    mythtv       4096 2011-10-08 22:21 mythtv

Hope that helps!


Users / Re: mythconverg_bac out of control
« on: December 16, 2011, 06:17:43 pm »
You can stop an upstart job with:

sudo stop {service name}

Restart it with sudo start {service name}.

To disable it once already stopped, you can either

sudo mv /etc/init/{service}.conf /etc/init/{service}.conf.noexec


sudo update-rc.d {service} disable

(doing it again with enable at the end will re-enable it)

Hope that helps!


Users / Re: mythconverg_bac out of control
« on: December 14, 2011, 05:57:28 pm »
A couple of possibilities for you:

Disable the upstart job that starts mythtv-backend.  Upstart has service supervision, so if the backend keeps dying, upstart will restart it (kind of like monit or daemontools).

Rename the mythtv-backend binary.  Then you can launch it from a terminal with debugging turned on.  I'm not in front of my system right now, so I can't say for certain what the binary is called.  I think it's mythtv-backend.

Hope that helps!


Users / Re: Live Tv Menu
« on: November 21, 2011, 10:17:37 pm »
I have a 19 month old and 3 month old. The 19 month thinks his bedtime isn't until 11:00 :)

It'll get a bit better when they get into kindergarten... it tuckers them out pretty good.  Until then, you're it!  ;-)

Thom, Posde, or gogol4,

Given that it's undergoing inital dev in 10.04, is the plan to make qOrbiter the new orbiter for 12.04?  Will the old one be deprecated or removed when qOrbiter becomes the default?

Just curious...

/Mike (aka parental play structure unit known to two as DAD ;-)

Pages: 1 ... 9 10 [11] 12 13