Software :: TRAC - Bug System Errors In Module Template
Mar 5, 2010
For some reason, my users are complaining that TRAC - our bug systems is throwing errors when looking for its module templates. These templates are usually built by Apache when it restarts or reloads and it puts them in /tmp/.python_eggs. I did a df-h and the drives had plenty of space, but the concerning thing is tmpfs shows 0% used.. We have not had a power outage or or restart in over a few months. I thought perhaps TMPwatch is clearing though, but there are no logged messages in the logs.
I have debian SID,my repository has libapache2-mod-python version 3.3.1-9+b1 and python 2.6.6-6 No, i configured my apache and restarted my apache, but i saw following errors in the apache's log file:
[Sat Oct 30 15:14:06 2010] [error] python_init: Python version mismatch, expected '2.6.5+', found '2.6.6'. [Sat Oct 30 15:14:06 2010] [error] python_init: Python executable found '/usr/bin/python'. [Sat Oct 30 15:14:06 2010] [error] python_init: Python path being used '/usr/lib/python2.6/:/usr/lib/python2.6/plat-linux2:/u
i can't downgrade my python and my libapache2-mod-python is last version.
I need to install Trac on a server that's on a private development VLAN (no internet access). Obviously Trac needs to go out over the internet to download/install various things. Does anyone know of an RPM or tarball out there that I can use to install Trac without being connected to the net?
I have Mythbuntu 10.04 installed on an exclusive HTPC and working great... until tonight. After letting the system update some packages (161 packages if I remember right), I suddenly have an issue where the graphical system won't start. After researching I found three error messages that might be causing that.
1. At the start of splash screen I see "UUID=xxxxxxxCD7 not ready yet or not present" I checked in /etc/fstab and found that this is the swap partition. I don't remember seeing this before so this could be the culprit.
2. I'm not at the computer in question right now but I saw a Plymouth error about "mountall" and then the message "plymouth command failed". Not sure if this could be the main error.
3. after a while (usually ca. 1-2 min) I receive thousands of errors of the kind "out of memory"... "kill process XXXX" (process vary wildly e.g. dbus-daemon, mysql, etc)... "process killed"..."respawning"
After error 3, I'm not able to switch to graphical console (ctrl-alt-F7). If I was in the graphical console at this moment, I simply can't switch to the CLI console. I'm always afraid of updating my system since I've seen lots of things breaking afterwards (usually the proprietary graphic drivers) but this is really strange.
I get this error when I run gedit as root in terminal. GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See GConf configuration system for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
So I looked around and found something about running a system check. Well I really couldn't find to much but I did find the command fsck and running it with the -n option this is what I got.
[Code]...
As you can see I have some orphaned inodes and these are probley from a Yast2 crashing a couple of times on me getting lockup because a repo was down or not responding.
I`m trying to compile sources of kernel module which has been written for kernel 2.6.9. There were many changes in kernel headers since then in current kernel sources. I`ve found that old /asm/system.h was moved under architecture dedicated directory /arch/*/include/asm/system.h. Anyway during sources compilation I`m having errors related to kernel sources. It looks like there is something wrong with this /asm/system.h
Code:
../asm/system.h: In function �__cmpxchg�: ../asm/system.h:248: error: expected string literal before �LOCK_PREFIX� ../asm/system.h:254: error: expected string literal before �LOCK_PREFIX�
After the updates about a week ago I noticed my system was hanging (screen and mouse frozen, unable to switch desktops, trl+Alt+SysRq+B still reboots) frequently. Though sometimes the system would not hang but become extremely sluggish and unresponsive. I've been able to determine that the problems occur whenever a module is added or removed. I can cause this problem with such commands as:
sudo modprobe aes sudo rmmod raid0
I've tried multiple kernels but the problem persists. I've run memtest on the system but no errors have been found. I wonder if this could be some other sort of hardware problem but I'm suspicious that this began after a set of updates. I've seen message such as this in the kern.log:
Code:
Jun 25 22:35:48 localhost kernel: [ 240.480059] INFO: task modprobe:2672 blocked for more than 120 seconds. Jun 25 22:35:48 localhost kernel: [ 240.492925] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 25 22:35:48 localhost kernel: [ 240.506918] modprobe D 00000000ffffffff 0 2672 2650 0x00000004
[code]....
I've tried using strace but that was not helpful. This is becoming a serious problem as I cannot load any encrypted volumes due to the inability to load the aes module. dpkg is currently in an interrupted state as the system hung when upgrading virtualbox-3.2 when it attempted to remove the modules. So my system is barely functional and I cannot see any way to fix things.
I'm doing a custom version of mod_musicindex, but can't get the cache to write like it's supposed to.example cache file: /tmp/testing/cacheNow, normally I think setting the dir testing and file cache to www-data:www-data would be enough. Permission denied. I tried 666 as well, figuring why not. Permission denied.777 works, but thats pretty far out there...Am I using the wrong user/group? I figured apache modules would run as apache.Do I need to use 777? 700 or 744 don't work, which is making me think it's not running as apache...
my Conky needed the Coretemp, and a friend of LQ told me to run modprobe, and it works greate! no every time I start my system, I need to run the modprobe to add the module to Kernel. How can I put the coretemp to start every startup? (I think there is somenthing to do with a file on the rc.module at /etc/rc.d/, but I'm afraid to do something stupid...) I want to make the conky running after start of the system. How can I do this?
I'm aware of Linux ECC project, but how to detect ECC errors/warnings under Linux? Do I need to load additional modules in order to get this information?
I'm using Ubuntu 9.10 with kernel 2.6.31 and gcc 4.4.1. I began getting the following errors from gcc after installing bison, g++ and g++-multilib and also after compiling 2.6.34-rc3 as a test. I've tried removing the packages but the error still shows up.
The module e1000e is loaded into system. At addition VLAN the system hangs at a stop VLAN or configure other devices (sound, video). In OpenSuSe 11.3 it worked correctly. MB: ASUS P5Q-ME DO / NetCard: Intel 82567LM-3
i have check /etc/pam.d/system-auth for the "ccount" entry, but it does not exist. "ccount" existed before in /etc/pam.d/system-auth but i managed to change it back to "account." i have grepd for the "ccount" string in all files under /etc/pam.d and i was not able to find it.
it seems that the system-auth is not able to take the now "account" string insted of "ccount" altough i have restarted crond
here is my system-auth file on the affected server:
i have check /etc/pam.d/system-auth for the "ccount" entry, but it does not exist. "ccount" existed before in /etc/pam.d/system-auth but i managed to change it back to "account." i have grepd for the "ccount" string in all files under /etc/pam.d and i was not able to find it. it seems that the system-auth is not able to take the now "account" string insted of "ccount" altough i have restarted crond here is my system-auth file on the affected server:
We have an old server running, and I decided to run fsck.ext3 -n on the disk to check it (while it was running). Turns out it reports lots of errors - not a good thing.
The weird thing is that when booting up a rescue cd and running fsck.ext3 on it, it says there are no problems with it. The filesystem is marked clean. Forcing a check with -f turns up nothing.
Now, when booting it from disk, fsck complains about an unclean file system that has not been checked for like 50000 days (obviously an error). Running e2fsck -n /dev/sda2 turns up errors again - not necessarily the same ones as the last time.
This makes me wonder: Can running e2fsck on a mounted file system cause errors? I ran with -n which is not supposed to do anything, just doing a read-only check. On the other hand, I heard checking a live file system might throw erros since the files being checked might change while bign checked, thus causing false positives.
Can the old version of e2fstools (1.38, approx 2005) mean non-existing errors are shown? Both the rescue cd and the system use this version.
In any case - why would the file system report errors on boot-up when the rescue cd just said it was ok? It should have been marked clean by now.
For laughs, I shut down the system and booted Knoppix which has a quite recent version (1.41.12, May 2010) of e2fstools. It showed no errors on the file system.
What do you think - are there errors or not on the file system?
The system is actually running Suse, but this is not about Suse specific things - just general Linux tools. And I use Ubuntu personally.
an old Compaq Presario 8000, which I reluctantly took, as I tend to end up with more computers than I use and more or less end up acting as a disposal agent. It's a 2.4Ghz machine, which will suffice for whatever I felt like installing on it.I have a generic wifi pci card with a Realtek RTL8185 chipset in it, which I never used and thought I'd set up that computer with it. Hadn't installed Slackware 13 on anything, and it's a distro I like so I went at it.Install went well, no problems there, but I've used Slackware for about 9 years so I'm readily familiar with that end o' things.
I found the rtl8180 module to be causing problems. It would load on boot, but wouldn't bring up a wireless interface. I was able to remove the module with 'rmmod rtl8180' well enough, but when I would load it again with 'modprobe rtl8180', the system would lock. Tried that a few times, same result. I ran across mention of a driver on Realtek's web site, so I downloaded and installed it. That one is identified as 'r8180'. I added 'rtl8180' to the module blacklist to prevent it from being loaded at boot, and proceeded to set up wpa_supplicant.conf for my WPA-PSK connection. Came up without a hitch.The connection is stable thus far, with a respectable link quality. The Realtek driver can be found here.I thought I might document my solution here in case someone else runs across the same issue that I experienced.I'm thinking of slapping another wireless NIC in that computer, or perhaps testing with multihoming possibly. This computer will probably end up as an AP for relaying my wireless traffic to an AP downstairs. I have one USB NIC (Alfa AWUS036S)with a 5dB antenna that has a strong signal, but the ones of more a common variety could use a little help
i get file system errors on boot up. found logs in /var/logs but cant access them. second best thing i can do is to re-install debian but no one seems to want to say how thats done. my disk wont run in wine (some error i dont remember) so i cant use my CD /flashdrive to re-install.
1) i need to read the log files and try to fix the install 2) if i cant fix i need to know how to wipe the OS and do a fresh install
Does anyone know where there might be a log of the shutdown errors I see flash on the screen when I shutdown the system? I thought they'd be in the warning log. Or is there a way to freeze that screen so I can actually read what is happening?
Could not download all repository indexes. The repository may no longer be available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and ensure the repository address in the preferences is correct.
Recently, I decided to migrate from SuSE 11.2 to 11.4. My 11.2 installation was working fine with two VLANs and several VMs. I went the route of installing 11.4 from scratch rather than upgrading 11.2.
The installation went smoothly. Afterwards, I ran Yast and changed eth0 to a bonding interface. Then I added two VLANs that used the bonding interface. When I restarted the computer, I saw the following on the console: "Waiting for mandatory devices vlan3005 __NSC__". Then after a 30 second countdown:
"vlan3005 no interface found". The solution to that problem was to add "ETHERDEVICE='eth0'" to /etc/sysconfig/network/ifcfg-eth0.3005". Upon restarting the computer, I could see that DHCP started this time but didn't get an IP address and continued in the background while the rest of the console messages scrolled by. At the point where X kicks in and I should have gotten a GUI login window, the screen goes dark. I cannot get to a console (CTRL-ALT-F1 or F2) or any other GUI login window (CTRL-ALT-F7 F8 or F9).
The computer was completely unresponsive. I could not ssh in to it from another host nor could I ping it. I let it sit for a few minutes but nothing ever appeared on the console. There were no blinking lights on the keyboard. I had to power the computer off. I turned off VLAN trunking on the switch port and the computer booted up fine, without network access, of course. I checked the logs but could find no clues as to what happened. I suspect a kernel problem. However, before I proceed further, I thought I would post my problem here and see if anyone has had a similar problem and perhaps a solution.
I've been using this scanner on various suse builds all the way back to version 8. This week I installed OpenSuse on a brand new computer and when I run xsane, I receive these messages.
[Code]....
The scanner will scan for a few seconds and then the entire system freezes up.
