I had a dedicated HTPC box running Mythbuntu 11.04 (MythTV 0.24.1, I believe) that was both a master backend and frontend. I was also running a separate box (server 10.04) as a file server, print server, etc. Very recently I decided to try to migrate the backend duties and database from the HTPC box to the server so that I only need to have one machine running 24/7. So, on the server, I installed mythtv-backend-master from the repository, which for 10.04 is version 0.23.0+fixes. You might have seen this one coming... when I try to import the database from the Mythbuntu box into the server's MythTV installation, I get an error message saying the database schema (1264) is newer than expected (1254).
So, I'm wondering about my options at this point. Is it reasonable to install the same version of MythTV on the server? What would be the best way of going about that?
Is there a way to easily revert the database schema to the earlier version that's required?
Will I just need to start over with a new database? (Hopefully not this one.)
I'm trying to setup Mythbuntu on a computer connected to a TV. I have bought an USB DVB-T Receiver, named WandTV. According to LinuxTV; WandTV, aka Shenzhen Forward Video EzTV859, is supported in the Linux kernel.
When I try to setup the mythTV backend I'm being asked of what card type I have. I guess the answer to that is "DVB DTV capture card (v3.x)", but no matter what I choose, it can't find any devices.
I'm pretty sure /dev/hidraw0 is the receiver, can I use that to setup the backend?
Like the title stated Anyone with experience or suggestion, please do share. I've tinkered all night with this thing. Never get the VBox service I created to start.Here is my final code before I dried my brain.
I installed MySQL and Apache2 to develop & test out the site I'm writing. However since I'll be using them purely for internal use (not exposed to the Net), I don't want them to start with every boot-up, but would like to start them manually when I desire, and stop them after use.With previous Ubuntu (Jaunty) I'd used chkconfig to configure services, but since the current version (Maverick) uses Upstart, is chkconfig still applicable?
I also installed 'bum' (Boot-Up Manager), but strangely, it displays the MySQL server as "unchecked" even though it's running (and starts at boot-up), so I cant see how I can prevent it from starting at boot-up through bum. chkconfig also displays MySQL as not active at runlevel 5, when in fact, it is.
I'd like to know what's the recommended (official) way to configure boot-up services with the Upstart system? I don't suppose directly editing the *.conf files in /etc/init is the best (or even correct) way?
On Maverick + up-to-date on updates on Mini ITX (Asus AT3N7A-I) I have a Perl script that I want to run continually to extract values from XML that appears on a USB port every 5 seconds and stuff the extracted values into an RR Database (RRD). I have created an Upstart job, called currentCost.conf (permissions=644 owner=root): #readCurrentCostData4RRD.pl daemon
description "regular background program processing daemon"
start on runlevel  stop on runlevel [!5] expect fork respawn exec perl /home/greg/currentCost/readCurrentCostData4RRD.pl > /tmp/RCCD4RRD.out 2>&1
Code: root@tux:~# start smbd smbd start/running, process 16067 root@tux:~#
oh and stop firestarter. Ok the firewall issue, is probably simple. I am more concerned that an upstart task won't start. I have checked in boot-up manager, and it is asked to start. This was an upgrade from Lucid, where I hadno problems.
I want to install GTK+. I see there are also numerous dependencies, which i've been slowly tackling, and the Cairo package has been particularly difficult. It claims the following upon ./configure --prefix=/usr configure: WARNING: Could not find libpng in the pkg-config search path checking whether cairo's PNG backend could be enabled... no configure: error: requested PNG backend could not be enabled I've done some searching and found that libpng.pc is in my /usr/lib/pkgconfig/ directory and that the following commands don't do the trick:
Eclipse cannot start and I can see the following in the log: java.version=1.6.0_22 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 !ENTRY org.eclipse.osgi 2 0 2011-07-09 15:01:23.881 !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved: ..... and etc. those files are actually in /usr/lib64/eclipse/plugins/ but system cannot find them as I see.
It happened after I played with Eclipse's software configs and broke some dependencies there. After I tried removing and reinstalingl eclipse I notices that /usr/lib64/eclipse files don't change and I have the same broken sortware install configuration. So I deleted the folder usr/lib64/eclipse and reinstalled Eclipse. It didn't work. I restored usr/lib64/eclipse from eclipse~ and now see that error log. What is the way to fix it or probably remove eclipse completely and reinstall that /usr/lib64/eclipse/ becomes as it was by default.
I seem to be having some issues. I want to do the following. I want a script to run prior to any GUI starting (so that if it does crash close or whatever it is not effected).I am able to run the script after the system is booted and it works exactly as I want it to. Once the GUI opens I have a window open and maximize with no decoraction via devilspie. This way I have a desktop that can monitor the logs but not interact directly interact with the shell which is actually recording the logs.
The problem is, when I try and use a simple Upstart script to start it the script does not seem to be working. If I do a ps -A it seems to be still running. What it should be doing is recording what the serial input to the log file I am using. In fact... it doesn't seem to be capturing anything. If I try and run the script manually after the computer has booted (with the Upstart script run) to a GUI it crashes the system.The script I am running is simply to record any incoming data from a Serial connection. It sets up the serial port then starts recording.The shell script is as follows:
Very frustrated. I have used Unix for ages so I understood the SysV startup stuff. But I have not had a lot of luck with Upstart. The other day I noticed that on every reboot my disks are getting fsck'd. I just recently put an ext2 on /tmp so this takes a while (the ext4 drives just rip through their journals).
The problem is no one is unmounting them on a KDE restart (4.X). I started out looking at /etc/init.d/umountfs and putting some logging in there. It never runs. This is despite that /etc/init has an upstart job that is supposed to run all the runlevel stuff.
I also tried to log some info in /etc/init/mountall-shell.conf which looks like it tries to do a umount -a on shutdown (which is probably not a good idea; you need to unmount in a particular order). That doesn't seem to happen either. I am not even sure how to troubleshoot this further. I suppose I need to see if the reboot( command has the same problem. Or if I shut down kdm first if it goes away.
I have run into a problem that I've tracked down to being a conflict between the "Upstart" init system, and how it handles multiple (alias) IP addresses per physical interface. The summary of the problem is that the interfaces are being configured in the background in parallel with the starting of daemons. One "feature" of this (apparently intended for pluggable devices that would add or remove an interface) is that the network daemons are restarted each time an interface is added (and presumably deleted). But this is a disaster when applied to alias IP addresses.
I first saw the effects of this when during booting Ubuntu Server, the screen showed a message about OpenSSH daemon being restarted ... several times a few seconds apart each. At the time I didn't know what was causing that, but didn't worry because it ultimately was running when I needed it.
But now that I am deploying these servers for specific duty with many IP addresses per system (per network interface), the symptoms are becoming serious, and I need a solution.
1. The IP addresses are coming online too slowly. Apparently the time it takes to restart each daemon is being added to each address being configured.
2. It appears to be disrupting some daemons sometimes. Occaisionally, some daemon just ends up being hung somewhere, or dies. Too many restarts.
3. Sometimes few or even no alias addresses get configured. This might be due to a daemon getting hung, and the whole sequence just not finishing.
4. The "nsd" name server as packaged by Ubuntu doesn't deal well with this at all. It needs all its IP addresses to be up when it starts, or else it won't start. The Ubuntu package of it doesn't including any if-up script at all, although I'm not sure that would do any good.
What I need is a way to configure all these alias IP addresses so they are all configured immediately when the point in time is reached to bring up network interfaces for the first time. These are all static, and all are aliases on ethernet NIC cards plugged into PCIe cards, or integrated in the mainboard. None of them are pluggables. I did run a manual test of "ifconfig" in a loop configuring 2540 alias IP address on eth0 and it only took 2 seconds (no if-up triggers or daemon restarts here). So I know it's fast if nothing else is done between these steps.
Even for pluggable physical interfaces, I see no reason to even try to step through every alias (if it has aliases) with a daemon restart. If an alias IP address is added on later, then I can understand doing it. But if you have a list of 100 aliases for a physical interface, they really should all be done ... or at least attempted ... at once, and do any triggers needed after that.
So, how can I configure or modify Ubuntu Server 9.10 to do that?
I have each alias listed in the "/etc/network/interfaces" file with a separate "auto" and "iface" section for each one, with sequential sub-interface numbers appended to the interface name. I tried it without those sections (e.g. just "address" and other items in sequence) and that prevents the system from even coming up (bootable CD to the rescue to undo that). At least cntrl-alt-del did reboot it.
I tried to attach the /etc/network/interfaces file, but I don't know if it worked because I see no confirmations about it. if it didn't attach and you need to see it, say so, and I'll just paste it in a followup.
I recently discovered upstart is launching sshd on my machine even though I disabled it with `sudo update-rc.d -f ssh remove`. I tried to find a way to prevent upstart from launching ssh by default, but the best I can think of is removing /etc/init/ssh.conf (I just uninstalled openssh-server).I'd like to disable it without doing this, though. This would make it easier to enable sshd when I need it
From what I've read, it appears that the respawn stanza in /etc/init/mysql.conf would give me the restart option if the daemon crashes, but I want to make sure other safety features of mysqld_safe are present as well.My /etc/init/mysql.conf is the original. I've tried changing the exec stanza from /usr/sbin/mysqld to /usr/sbin/mysqld_safe but the job fails when I sudo service mysql start.mysql.conf
Has anyone got a working apache upstart script? I'm running 10.04, and want the nice supervision stuff from upstart to run my apache instance. I've googled (especially for things like replacement-initscripts) but not hit anything concrete.
I'd like to create a couple of upstart scripts for some network service daemons (eg. usenet downloading service, torrent service, media management services, etc).Basically they should start after the network service is started and the system is running (runlevel 2?) but I'm just wondering if anybody has an example script or more specific start/stop conditions that I can use.
I have posted this somewhere here before and solved it but can't seem to find it. Just waisted 50 minutes googling and checking man pages for upstart. By the way; are man pages written by someone using their tows to type and getting beaten by a stick for every character they type? It seems missing a lot of info. Anyway, I know smbd is started with /etc/init/smbd.conf and there is a line like:
Code: start on local-filesystems Now it needs to be started on? (manually) I can't seem to find any useful information but did seem to find the upstart man pages a hundred times or so (same info same missing parts). I would love to get involved writing documentation for these things if only I know what I was doing.
Because of my problem here:[URL]..I'd like to replace upstart with systemd on F14. Is this as simple as a yum install? In the wiki is it's referred to as a "technology preview" for F14, which is meaningless to me; there are no further notes about installing or enabling it.
I have the following problem: There are three NFS mounts in /etc/fstab, which are automatically mounted. The network connection runs over NetworkManager. Since NWM brings up the network asynchronously, NFS doesn't mount correctly on the first try, but is loaded soon enough since mount automatically retries until it works.
I can live with the fact that I have an error in my boot messages, since everything is up in time for the user. But, I need a (selfmade) upstart script which depends on the NFS mount being up. Even using "remote-filesystems" as the trigger doesn't help, because the trigger is apparently sent after the first failed try (I checked with cat /proc/mounts in my script, the nfs mounts are clearly not up.) Can I somehow force the remote mounts to wait until NWM is up, or make the NFS mount emit an event when the mounts really get mounted?