[SOLVED]can't start X after full upgrade

I just recently updating arch linux on X41 Tablet (i686, cpu=pentium m)..
after restarting, i can't startx.
it says
Loading extension GLX
AIGLX: Suspending AIGLX clients for VT switch(EE) Server terminated with error (1). Closing log file.onal information. (EE) (II)
^Cxinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: unexpected signal 2
here's the Xorg.0.log
[ 170.079] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 170.079] (EE)
Fatal server error:
[ 170.079] (EE) failed to create screen resources(EE)
[ 170.080] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 170.080] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 170.080] (EE)
[ 170.080] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 170.109] (EE) Server terminated with error (1). Closing log file.
and here's pacman.log today
[2014-06-17 12:05] [PACMAN] Running 'pacman -Syyu'
[2014-06-17 12:05] [PACMAN] synchronizing package lists
[2014-06-17 12:05] [PACMAN] starting full system upgrade
[2014-06-17 13:01] [PACMAN] upgraded perl (5.20.0-2 -> 5.20.0-4)
[2014-06-17 13:01] [PACMAN] upgraded openssl (1.0.1.g-1 -> 1.0.1.h-1)
[2014-06-17 13:01] [PACMAN] upgraded sqlite (3.8.4.3-2 -> 3.8.5-1)
[2014-06-17 13:01] [PACMAN] upgraded aircrack-ng (1.1-10 -> 1.2beta3-1)
[2014-06-17 13:01] [PACMAN] upgraded arpwatch (2.1a15-13 -> 2.1a15-14)
[2014-06-17 13:01] [PACMAN] upgraded binutils (2.24-4 -> 2.24-6)
[2014-06-17 13:01] [PACMAN] upgraded cifs-utils (6.3-1 -> 6.3-2)
[2014-06-17 13:01] [PACMAN] upgraded gcc-libs (4.9.0-3 -> 4.9.0-4)
[2014-06-17 13:01] [PACMAN] upgraded llvm-libs (3.4.1-2 -> 3.4.2-1)
[2014-06-17 13:01] [PACMAN] upgraded llvm (3.4.1-2 -> 3.4.2-1)
[2014-06-17 13:01] [PACMAN] upgraded isl (0.12.2-1 -> 0.13-1)
[2014-06-17 13:01] [PACMAN] upgraded cloog (0.18.1-2 -> 0.18.1-3)
[2014-06-17 13:01] [PACMAN] upgraded gcc (4.9.0-3 -> 4.9.0-4)
[2014-06-17 13:02] [PACMAN] upgraded clang (3.4.1-2 -> 3.4.2-1)
[2014-06-17 13:02] [PACMAN] upgraded cmake (2.8.12.2-2 -> 3.0.0-3)
[2014-06-17 13:02] [PACMAN] upgraded libdbus (1.8.2-1 -> 1.8.4-1)
[2014-06-17 13:02] [PACMAN] upgraded dbus (1.8.2-1 -> 1.8.4-1)
[2014-06-17 13:02] [PACMAN] upgraded libsystemd (213-5 -> 213-9)
[2014-06-17 13:02] [PACMAN] upgraded systemd (213-5 -> 213-9)
[2014-06-17 13:02] [PACMAN] upgraded mesa (10.1.4-1 -> 10.2.1-2)
[2014-06-17 13:02] [PACMAN] upgraded mesa-libgl (10.1.4-1 -> 10.2.1-2)
[2014-06-17 13:02] [PACMAN] installed json-glib (1.0.2-1)
[2014-06-17 13:02] [PACMAN] installed libnm-glib (0.9.8.10-3)
[2014-06-17 13:02] [PACMAN] installed libmm-glib (1.2.0-4)
[2014-06-17 13:02] [PACMAN] installed geoclue2 (2.1.8-2)
[2014-06-17 13:02] [PACMAN] upgraded giflib (5.0.6-1 -> 5.1.0-1)
[2014-06-17 13:02] [PACMAN] upgraded libwebp (0.4.0-1 -> 0.4.0-2)
[2014-06-17 13:02] [PACMAN] upgraded webkitgtk2 (2.4.2-1 -> 2.4.3-1)
[2014-06-17 13:02] [ALPM-SCRIPTLET] ==> If you are using extensions you should update the extensions with
[2014-06-17 13:02] [ALPM-SCRIPTLET] ==> dwbem -u or dwbem -Nu
[2014-06-17 13:02] [PACMAN] upgraded dwb (2014.03.07-1 -> 2014.03.07-2)
[2014-06-17 13:02] [PACMAN] installed libx264 (1:142.20140311-4)
[2014-06-17 13:02] [PACMAN] upgraded x265 (1.0-1 -> 1.1-1)
[2014-06-17 13:02] [PACMAN] upgraded ffmpeg (1:2.2.3-1 -> 1:2.2.3-2)
[2014-06-17 13:02] [ALPM] warning: /etc/group installed as /etc/group.pacnew
[2014-06-17 13:02] [ALPM] warning: /etc/passwd installed as /etc/passwd.pacnew
[2014-06-17 13:02] [PACMAN] upgraded filesystem (2013.05-2 -> 2014.06-1)
[2014-06-17 13:02] [PACMAN] upgraded gc (7.4.0-3 -> 7.4.2-1)
[2014-06-17 13:02] [PACMAN] upgraded geoip-database (20140304-1 -> 20140604-1)
[2014-06-17 13:02] [PACMAN] upgraded gnupg (2.0.22-2 -> 2.0.23-1)
[2014-06-17 13:02] [PACMAN] upgraded gparted (0.18.0-1 -> 0.19.0-1)
[2014-06-17 13:02] [PACMAN] upgraded grep (2.19-1 -> 2.20-1)
[2014-06-17 13:02] [PACMAN] upgraded hunspell (1.3.2-3 -> 1.3.3-1)
[2014-06-17 13:02] [PACMAN] upgraded imlib2 (1.4.6-1 -> 1.4.6-2)
[2014-06-17 13:02] [PACMAN] upgraded intel-dri (10.1.4-1 -> 10.2.1-2)
[2014-06-17 13:03] [PACMAN] upgraded jre7-openjdk-headless (7.u55_2.4.7-1 -> 7.u60_2.5.0-2)
[2014-06-17 13:03] [PACMAN] upgraded xdg-utils (1.1.0.git20140207-1 -> 1.1.0.git20140426-1)
[2014-06-17 13:03] [PACMAN] upgraded jre7-openjdk (7.u55_2.4.7-1 -> 7.u60_2.5.0-2)
[2014-06-17 13:03] [PACMAN] installed librevenge (0.0.1-2)
[2014-06-17 13:03] [PACMAN] upgraded libwpd (0.9.9-1 -> 0.10.0-1)
[2014-06-17 13:03] [PACMAN] upgraded libcdr (0.0.16-2 -> 0.1.0-1)
[2014-06-17 13:03] [PACMAN] upgraded libetonyek (0.0.4-1 -> 0.1.1-1)
[2014-06-17 13:03] [PACMAN] upgraded libevdev (1.2.1-1 -> 1.2.2-1)
[2014-06-17 13:03] [PACMAN] upgraded libgdiplus (2.10.9-4 -> 2.10.9-5)
[2014-06-17 13:03] [PACMAN] upgraded libice (1.0.8-2 -> 1.0.9-1)
[2014-06-17 13:03] [PACMAN] upgraded libmspub (0.0.6-2 -> 0.1.0-1)
[2014-06-17 13:03] [PACMAN] upgraded libodfgen (0.0.4-1 -> 0.1.1-1)
[2014-06-17 13:03] [PACMAN] upgraded libproxy (0.4.11-3 -> 0.4.11-4)
[2014-06-17 13:03] [PACMAN] upgraded libreoffice-en-US (4.2.4-1 -> 4.2.4-2)
[2014-06-17 13:03] [PACMAN] upgraded libreoffice-common (4.2.4-1 -> 4.2.4-2)
[2014-06-17 13:03] [PACMAN] upgraded libreoffice-base (4.2.4-1 -> 4.2.4-2)
[2014-06-17 13:03] [PACMAN] upgraded libreoffice-calc (4.2.4-1 -> 4.2.4-2)
[2014-06-17 13:03] [PACMAN] upgraded libreoffice-draw (4.2.4-1 -> 4.2.4-2)
[2014-06-17 13:03] [PACMAN] upgraded libreoffice-gnome (4.2.4-1 -> 4.2.4-2)
[2014-06-17 13:03] [PACMAN] upgraded libreoffice-impress (4.2.4-1 -> 4.2.4-2)
[2014-06-17 13:03] [PACMAN] upgraded libreoffice-math (4.2.4-1 -> 4.2.4-2)
[2014-06-17 13:04] [PACMAN] upgraded libreoffice-writer (4.2.4-1 -> 4.2.4-2)
[2014-06-17 13:04] [PACMAN] upgraded libwpg (0.2.2-2 -> 0.3.0-1)
[2014-06-17 13:04] [PACMAN] upgraded libvisio (0.0.31-3 -> 0.1.0-1)
[2014-06-17 13:04] [PACMAN] upgraded libwps (0.2.9-1 -> 0.3.0-1)
[2014-06-17 13:04] [PACMAN] upgraded libxft (2.3.1-2 -> 2.3.2-1)
[2014-06-17 13:04] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-06-17 13:04] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> Starting build: 3.14.6-1-ARCH
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> Starting build: 3.14.6-1-ARCH
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-06-17 13:04] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2014-06-17 13:04] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-06-17 13:04] [PACMAN] upgraded linux (3.14.5-1 -> 3.14.6-1)
[2014-06-17 13:05] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-06-17 13:05] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> Starting build: 3.10.43-1-lts
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts.img
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> Starting build: 3.10.43-1-lts
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-06-17 13:05] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts-fallback.img
[2014-06-17 13:05] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-06-17 13:05] [PACMAN] upgraded linux-lts (3.10.41-1 -> 3.10.43-1)
[2014-06-17 13:05] [PACMAN] upgraded linux-lts-docs (3.10.41-1 -> 3.10.43-1)
[2014-06-17 13:05] [PACMAN] upgraded linux-lts-headers (3.10.41-1 -> 3.10.43-1)
[2014-06-17 13:05] [PACMAN] upgraded man-pages (3.68-1 -> 3.69-1)
[2014-06-17 13:05] [PACMAN] upgraded mdadm (3.3-2 -> 3.3.1-2)
[2014-06-17 13:06] [PACMAN] upgraded mpv (0.3.10-1 -> 0.3.11-1)
[2014-06-17 13:06] [PACMAN] upgraded nspr (4.10.5-1 -> 4.10.6-1)
[2014-06-17 13:06] [PACMAN] upgraded python-setuptools (4.0.1-1 -> 1:5.1-1)
[2014-06-17 13:06] [PACMAN] upgraded python2 (2.7.6-3 -> 2.7.7-1)
[2014-06-17 13:06] [PACMAN] upgraded python2-mako (0.9.1-2 -> 1.0.0-1)
[2014-06-17 13:06] [PACMAN] upgraded s-nail (14.6.4-1 -> 14.7-1)
[2014-06-17 13:06] [ALPM-SCRIPTLET] Syslinux BIOS update successful
[2014-06-17 13:06] [ALPM-SCRIPTLET]
[2014-06-17 13:06] [ALPM-SCRIPTLET] ==> For setting up Syslinux BIOS using the syslinux-install_update script follow
[2014-06-17 13:06] [ALPM-SCRIPTLET] https://wiki.archlinux.org/index.php/Syslinux#Automatic_Install
[2014-06-17 13:06] [ALPM-SCRIPTLET]
[2014-06-17 13:06] [ALPM-SCRIPTLET] ==> For setting up Syslinux EFI follow
[2014-06-17 13:06] [ALPM-SCRIPTLET] https://wiki.archlinux.org/index.php/Syslinux#UEFI_Systems
[2014-06-17 13:06] [ALPM-SCRIPTLET]
[2014-06-17 13:06] [ALPM-SCRIPTLET] ==> The syslinux-install_update script does not currently support EFI install
[2014-06-17 13:06] [ALPM-SCRIPTLET]
[2014-06-17 13:06] [PACMAN] upgraded syslinux (6.03pre12-3 -> 6.03pre14-1)
[2014-06-17 13:06] [PACMAN] upgraded systemd-sysvcompat (213-5 -> 213-9)
[2014-06-17 13:06] [PACMAN] upgraded tp_smapi (0.41-46 -> 0.41-47)
[2014-06-17 13:06] [PACMAN] upgraded tzdata (2014d-1 -> 2014e-1)
[2014-06-17 13:06] [PACMAN] upgraded volumeicon (0.5.0-2 -> 0.5.0-3)
[2014-06-17 13:06] [PACMAN] upgraded wireshark-cli (1.10.7-2 -> 1.10.8-1)
[2014-06-17 13:06] [PACMAN] upgraded wireshark-gtk (1.10.7-2 -> 1.10.8-1)
[2014-06-17 13:06] [PACMAN] upgraded x264 (1:142.20140311-3 -> 1:142.20140311-4)
[2014-06-17 13:06] [PACMAN] upgraded xf86-video-intel (2.99.911-2 -> 2.99.912-1)
[2014-06-17 13:06] [PACMAN] upgraded xfce4-timer-plugin (1.0.0-1 -> 1.6.0-1)
[2014-06-17 13:06] [PACMAN] upgraded xfsprogs (3.1.11-2 -> 3.2.0-1)
[2014-06-17 13:06] [PACMAN] upgraded xscreensaver (5.26-1 -> 5.29-1)
[2014-06-17 13:06] [PACMAN] upgraded youtube-dl (2014.06.04-1 -> 2014.06.16-1)
[2014-06-17 13:07] [PACMAN] Running 'pacman -S mplayer'
[2014-06-17 13:07] [PACMAN] Running 'pacman -S mplayer youtube-viewer'
[2014-06-17 13:09] [PACMAN] installed mplayer (37224-1)
[2014-06-17 13:09] [PACMAN] installed perl-xml-fast (0.11-5)
[2014-06-17 13:09] [PACMAN] installed youtube-viewer (1:3.1.1-1)
[2014-06-17 13:12] [PACMAN] Running 'pacman -Sc'
help appreciated..
Last edited by veroke12 (2014-06-17 07:55:23)

amatriain wrote:Same here. Did you file a bug report?
kralyk wrote:
I had the same problem on a Dell laptop. Had to dowgrade to 2.99.911.
Did you guys file a bugreport?
not yet, i'm not sure if i have time to file a bugreport..
and not just the i686 version of xf86-video-intel 2.99.912-1 has problem, the x64 version seems to break the video rendering > https://bbs.archlinux.org/viewtopic.php?id=183052
Last edited by veroke12 (2014-07-08 15:23:45)

Similar Messages

  • [SOLVED] Can't Start MySQL after upgrading to 5.1.41-3

    I can't start mysqld with 'mysqld start'.Here is my mysqld output:
    [ahao@sky ~]$ mysqld start
    091125 18:33:48 [Note] Plugin 'FEDERATED' is disabled.
    091125 18:33:48 [Note] Plugin 'ndbcluster' is disabled.
    091125 18:33:48  InnoDB: Started; log sequence number 0 44233
    mysqld: Too many arguments (first extra is 'start').
    Use --verbose --help to get a list of available options
    091125 18:33:48 [ERROR] Aborting
    091125 18:33:48  InnoDB: Starting shutdown...
    091125 18:33:49  InnoDB: Shutdown completed; log sequence number 0 44233
    091125 18:33:49 [Note] mysqld: Shutdown complete
    This is my /var/lib/ complete with permission settings:
    [ahao@sky ~]$ cd /var/lib ; ls -al
    total 84
    drwxr-xr-x 20 root      root      4096 2009-11-25 18:08 .
    drwxr-xr-x 13 root      root      4096 2009-11-25 13:51 ..
    drwxrwx---  2 root      policykit 4096 2009-05-10 09:10 PolicyKit
    drwxr-xr-x  2 policykit root      4096 2009-05-10 09:10 PolicyKit-public
    drwxr-xr-x  3 root      root      4096 2009-09-19 12:19 bluetooth
    drwxr-xr-x  2 root      root      4096 2009-09-16 22:09 dbus
    drwxr-xr-x  2 root      root      4096 2009-11-23 17:38 dhcpcd
    drwxrwxrwt  2 root      root      4096 2009-07-19 18:17 ex
    drwxr-xr-x  2 root      root      4096 2009-09-16 22:38 hwclock
    drwxr-x---  2 root      locate    4096 2009-10-22 06:55 locate
    -rw-r--r--  1 root      root       462 2009-09-20 00:02 logrotate.status
    drwxr-xr-x  2 root      root      4096 2009-09-17 09:14 misc
    drwxr-x---  2 root      locate    4096 2009-11-25 18:09 mlocate
    drwxrwxrwx  4 mysql     mysql     4096 2009-11-25 18:33 mysql
    drwxr-xr-x  6 root      root      4096 2009-09-07 08:54 nfs
    drwxr-xr-x  4 root      root      4096 2009-11-25 18:08 pacman
    drwx------  3 root      root      4096 2009-11-21 03:30 polkit-1
    drwxr-xr-x  2 root      root      4096 2008-09-06 14:33 rarian
    drwxr-xr-x  2 root      root      4096 2009-09-17 09:14 syslog-ng
    drwxr-xr-x  3 root      root      4096 2009-10-19 20:10 wicd
    drwxr-xr-x  2 root      root      4096 2009-11-21 02:35 xkb
    /etc/mysql/my.cnf is out-of-the-box
    What seems to be the problem here? Please shed some light...thank you
    Last edited by akiglobal (2009-11-26 07:41:00)

    How silly of me.....first of all...I entered 'mysqld start', I should have just entered 'mysqld', second of all, I didn't change the file permission on /var/run/mysqld. I change /var/run/mysqld file permission into 'chmod 777 /var/run/mysqld -R', after that mysql works!

  • Can't start UCSM after java upgrade

    Hi
    After I have been recommended to upgrade to newest java, I can't start UCS Manager anymore.
    I try from a Windows 7 64 Bits computer and a Windows 8 64 Bits computer.
    Same error.
    As you see, I have java 1.7.0_07. It is higher than the reguirement.
    UCSM version is 2.0(2q)
    Because there is some security issues with earlier java versions, I don't want to downgrade.
    Do anyone have any solution on this problem?
    I have uninstalled every version of Java, and just installed the newest, but it didn't help
    Thanks for any help.

    Hi Sting,
    For you to use 1.7 you need to have UCSM version 2.0.3a and above.
    http://www.cisco.com/en/US/docs/unified_computing/ucs/release/notes/OL_25363.html
    (check the system requirement section).
    At this point, the only option for you is to downgrade back to a 1.6 version.
    ./Abhinav

  • [Solved]Can't start xwindow, after upgrade xorg

    It seems because of the fglrx driver...
    Last edited by wd_afei (2007-09-24 04:36:38)

    Couldn't figure out how to sort out disableabi (probably a good thing really ).
    In case anyone else comes this way, you'll probably at a minimum need to do roughly this:
    su
    cd /var/cache/pacman/pkg
    pacman -U xorg-server-1.3.0.0-7.pkg.tar.gz
    pacman -U xf86-input-keyboard-1.1.1-3.pkg.tar.gz
    pacman -U xf86-input-mouse-1.2.1-3.pkg.tar.gz
    your versions may differ from mine.  this seems to be enough to get things back on track until fglrx is updated (which I believe according to one forum post is due in October?)

  • Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved.  It started with the last upgrade to 10.8

    Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved.  It started with the last upgrade to 10.8

    Back up all data.
    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
    Step 1
    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
    Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
    Step 2 (optional)
    The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
    Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
    When the OS X Utilities screen appears, select
    Utilities ▹ Terminal
    from the menu bar. A Terminal window will open.
    In the Terminal window, type this:
    resetpassword
    That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not  going to reset a password.
    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
     ▹ Restart
    from the menu bar.

  • Can't Start Portal After Install

    After downloading and installing the of evaluation Portal 4.0 SP1, I get the following message upon startup when I enter the system password that I entered during installation:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: try to access method weblogic/management/internal/
    Helper.preloadMBeanInfos()V from class weblogic/management/Admin
    at weblogic.management.Admin.initialize(Admin.java:210)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    I even tried "weblogic" for the system password and I get the same message.
    What password should I use to start the server?

    I've followed the directions and am experiencing the exact same problem. Brand
    new installation of Weblogic server 6.1 SP2 with examples. That install is working.
    Then added Portal 4.0 SP1, updated the license file and I have the same issue
    with the Illegal access exception resulting in the "Fatal initialization exception"....
    Hmm!
    [email protected] (Bowrat) wrote:
    Below listed are the common errors you run into during installation
    process:
    - You need to have the correct version numbers of both the weblogic
    server and the portal server. For instance the portal server 4.0 (eval
    copy) will only run on WebLogic 6.1 SP1. So check the edocs for
    supported platforms
    - Make sure you have the installed the full version of the weblogic
    server (including examples)
    - Finally, you need to run the UpdateLicense.cmd file to update the
    license.bea under ur Bea Root
    Give it a shot after u have checked all of the above three - goodluck
    - Bowrat
    www.Bowstreet.com
    Steve Anderson <[email protected]> wrote in message news:<[email protected]>...
    From: Steve Anderson <[email protected]>
    Newsgroups: weblogic.support.install
    Subject: Can't Start Portal After Install
    References:
    NNTP-Posting-Host: 209.11.114.150
    X-Original-NNTP-Posting-Host: 209.11.114.150
    Message-ID: <[email protected]>
    Date: 13 Feb 2002 20:25:53 -0800
    X-Trace: 13 Feb 2002 20:25:53 -0800, 209.11.114.150
    Organization: BEA SYSTEMS Inc
    Lines: 18
    XPident: firewall-user
    Path: newsgroups.bea.com!209.11.114.150
    Xref: newsgroups.bea.com weblogic.support.install:9600
    After downloading and installing the of evaluation Portal 4.0 SP1,I get the following message upon startup when I enter the system password
    that I entered during installation:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: try to access method weblogic/management/internal/
    Helper.preloadMBeanInfos()V from class weblogic/management/Admin
    at weblogic.management.Admin.initialize(Admin.java:210)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    I even tried "weblogic" for the system password and I get the samemessage.
    What password should I use to start the server?

  • I have a 3gs and just updated my ios from 4.1 to 6.1.  But I can't activate it after the upgrade. heeeeelp!

    I have a 3gs and just updated my ios from 4.1 to 6.1. But I can't activate it after the upgrade. what to do?

    joycesalvador wrote:
    ... But I can't activate it after the upgrade. what to do?
    See this discussion.
    https://discussions.apple.com/message/21189708

  • Can't start Tomcat after installing Bea WorkShop for JSP

    Hi,
    I have been using Eclipse SDK Version: 3.1.2 Build id: M20060118-1600 and Web Tools Project 1.0.2 and Tomcat 5.0 and Tomcat 5.5 for about 2 months with no problems. But now I Can't start Tomcat after installing Bea WorkShop for JSP plug-in. I get "Server Tomcat v5.0 @ localhost failed to start". Any help would be greatly appreciated.

    I installed BEA Workshop for JSP Version: 3.1.0
    Build id: 536. I only wanted to install the plug-in to my existng Eclipse 3.1 / WTP application. The only option that I saw was to download the entire FullWorkshopFreeInstall-536.zip, which is 192,496 KB. During the installation, there is a screen that you can specify to only install the plug-in - and I selected that option. Today, I chose to uninstall the BEA Workshop for JSP and then I was again able to start Tomcat server. I then did a complete install of BEA Workshop for JSP into a totally separate location. My original Eclipse installation still works fine, but my Workshop for JSP Version (which is now a completely new installation) has the same problem with Tomcat that I reported with the plug-in. I am using j2sdk1.4.2_08 and have tried both Tomcat 5.0 and Tomcat 5.5. I have the same problem with both Windows XP Home Edition and Windows XP Professional.
    Thanks for your assistance.
    Ron

  • Why can't I print after I upgrade to MAC OS 10.10 (Yosemite)?

    Why can't I print after I upgrade to MAC OS 10.10 (Yosemite)?

    You need a printer driver upgrade. Check with your printer's manufacturer to see if they have a new driver available. If not, then ask their tech support for additional help.
    Meanwhile, open Print & Scan preferences, select the installed driver and click on the Delete [-] button. Then CTRL- or RIGHT-click in the list space and select Reset Print System from the context menu. Now, click on the Add [+] button to re-Add your printer. See it this helps. Be sure your printer is connected and turned on.

  • Can nort start  OC4J_BI_FORM  after Portal password change(9.0.4)

    We changed PORTAL password by going top sqlplus and OAS. Thinking it will make changes at both places. Now we see that when we start OAS. OC4J_BI_FORM does not start???

    I provided an answer in the Portal Security forum:
    Can not start OC4J_BI_FORM after PORTAL user password change

  • Hard disk problems after full upgrade [SOLVED]

    After a full upgrage (pacman -Suy) last monday, My system denied to boot:D:D:D:D:D.
    So to fix it I have to go to /boot/grub/menu.list and change from hda3 to sda3. Everything seems to be Ok but when the system is booting and scan the the hard disk to check bad, It drops me to the shell with the error that there is something wrong with my hard disk and it suggest me to set the superblock to 8139.
    So to fix it I boot my PC from Arch live CD, use the following command:
    #fsck.ext3 -c -f /dev/sda3
    #fsck.ext3 -b 8139
    Everything seems to be Ok, there is no bad in my hard disk.
    When I boot my system again, I got the same error again, I came back to live CD, check the hard disk, set the superblock as It told me and again, I got the error when I boot from the hard disk.
    This is the second PC with the same error.
    Three months ago, I upgraded my Server and got exactly the same problem. Because this is the server, I need it run ASAP, so I modified the rc.sysinit script so that the system will not check my hard disk when It boots. :P:P. And my Server can run without any problems since then.
    I don't have time much to spend on this error and my PC is in the Lab now so I can't provide the detail of the error until next Monday. Sorry for that.
    Any idea how to fix this error?
    Cheers.
    Last edited by hungsonbk (2008-06-25 10:26:35)

    tigrmesh wrote:Did you review and merge any .pacnew files after the upgrade?
    :D:D I am a kind of lazy guy so when I did pacman -Suy, I just leave it running without reading information on the terminal.
    milan wrote:I guess you didn't change entries in /etc/fstab (hda->sda).
    Yes, you are right. I changed from hda to sda in /boot/grub/menu.lst but I forgot to do the same in /etc/fstab files. On Monday I will check again if it is set correctly or not
    :D:D. I have just taken a quick look into the fstab file in my Server, The One with the same problem three months ago, and the fstab file is set correctly with sda partitions. I don't want to touch this server again or my services will be down. So this seems not the correct solution, but anyway, I will take a look at it next week.
    Thanks for your replies.

  • [SOLVED]Problem with logging in after system upgrade

    Hi,
    I'm encountering some problem after rebooting my machine just after last upgrade. Few minutes ago I was sure I found the source of the problem when system hang on "Reached target Graphical Interface" message. Reason - nvidia drivers had to be replaced with legacy version (https://www.archlinux.org/news/nvidia-340xx-and-nvidia/). But it didn't help. Also it made things a little bit worse. Because now my system uses nvidia-340xx and it seems drivers are fine but when login screen of lightdm should appear screens stay blank... and nothing happens. I simply can't do anything.
    What I noticed is also xfce4-session was upgraded (4.10.1.3->4.10.1-5) and maybe this is the separate problem? but I can't downgrade this package as some time ago I removed all contents of /var/cache/pacman/pkg.
    What I have is arch on pendrive so I can chroot into existing system.
    Any ideas?
    Last edited by jakub (2014-10-08 22:09:02)

    I found something similar to line
    (EE) Mar 07 14:05:07 NVIDIA(0): WAIT: (E, 0, 0x837d, 0)
    these values are not exact as I'm too tired now to rewrite the real ones from screen 
    maybe I should install some older nvidia drivers (these 340xx are broken somehow I think). Unfortunately I don't have my /pkg content anymore.
    Where can I download packages like nvidia-340.32-1-x86_64.pkg.tar.xz from? (according to pacman.log I had this version back in July and it was working fine I think).
    I could also start X with Nouveau drivers but not xfce (anyway I would like to install old nvidia drivers back)
    Last edited by jakub (2014-10-08 22:03:11)

  • Tuxedo not starting up after Database upgrade to 9.2.0.8 on AIX 5.2

    Hi All,
    Server AIX 5.2
    Database 9.2.0.8.
    I recently upgraded my Oracle database from 9.2.0.6 to 9.2.0.8 and after the upgrade Tuxedo has failed to start successfully.
    I am getting the error messages
    CMDTUX_CAT:819: INFO: Process id=41800 Assume started (pipe)..
    I have been reading a number of articles on metalink and the web and they seem to point to an incompatible version somewhere.
    The upgrade went through without any error messages.
    The strange thing is that the XA log files from when the application was working correctly before the upgrade show
    ORACLE XA: Version 9.2.0.1.0. RM name = 'Oracle_XA'
    in the headers of the logfiles however after the upgrade the info in the header has changed to
    ORACLE XA: Version 8.0.6.0.0. RM name = 'Oracle_XA'.
    Does anyone know any reason why the 9.2.0.8 patch will changed the Oracle_XA version?
    Has anyone come across this before?
    Please help.
    Mike

    Hi Madrid,
    Please note that the xa traces file name changes to non Y2K comnpatapable i.,e a 2 digit year after the upgrade
    $ ls -ltr xa*
    -rw-r--r-- 1 clsadm clsgrp 23854218 Jun 26 23:59 xa_CLSUAT06262007.trc
    -rw-r--r-- 1 clsadm clsgrp 28489952 Jun 27 23:59 xa_CLSUAT06272007.trc
    -rw-r--r-- 1 clsadm clsgrp 29461064 Jun 28 23:59 xa_CLSUAT06282007.trc
    -rw-r--r-- 1 clsadm clsgrp 28045125 Jun 29 23:59 xa_CLSUAT06292007.trc
    -rw-r--r-- 1 clsadm clsgrp 27560416 Jun 30 23:16 xa_CLSUAT06302007.trc
    -rw-r--r-- 1 clsadm clsgrp 4797139 Jul 01 23:59 xa_CLSUAT07012007.trc
    -rw-r--r-- 1 clsadm clsgrp 10007008 Jul 02 10:54 xa_CLSUAT07022007.trc
    -rw-r--r-- 1 clsadm clsgrp 8507 Jul 02 15:01 xa_CLSUAT070207.trc
    I know this may sound silly but after the upgrade (and this is the second time i have done it) it seems to change the format of the logfiles.
    This happened last week and the patch was rolled back and the application worked fine.
    Did the upgrade again and the same issue arose.
    The app dont start and the logfile format have changed again.
    The format before the upgrade was xa_CLSUAT_07022007 but after the upgrade it as changed to xa_CLSUAT_070207.
    The upgrade went fine but my question here is does the 9208 change any date format in the database?
    I am showing the contents of the xa* trace files before and after the upgrade.
    Before the upgrade
    ORACLE XA: Version 9.2.0.1.0. RM name = 'Oracle_XA'.
    194514.80870.0:
    xaoopen: xa_info=Oracle_XA+DB=CLSUAT+Acc=P/clsuser/ftech2+SesTm=7200+LogDir=/fundtech/cls/1.0.0/data/traces+DbgFl=0x7+SqlNet=CLSU
    AT,rmid=0,flags=0x0
    194514.80870.0:
    xaolgn_help: version#: 153093632 banner: Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.6.0 - Production
    194514.80870.0:
    xaolgn: sqlxrc/sqlxss completed
    After the upgrade
    ORACLE XA: Version 8.0.6.0.0. RM name = 'Oracle_XA'.
    150000.61956.0:
    xaoopen: xa_info=Oracle_XA+DB=CLSUAT+Acc=P/clsuser/ftech2+SesTm=7200+LogDir=/fundtech/cls/1.0.0/data/traces+DbgFl=0x7+SqlNet=CLSU
    AT,rmid=0,flags=0x0
    150001.61956.0:
    xaolgn_help: version#: 153094144 banner: Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.8.0 - Production
    150001.61956.0:
    xaolgn: sqlxrc/sqlxss completed
    150001.61956.0:
    xaolgn: return XA_OK
    As you can see the Oracle XA version has changed from
    ORACLE XA: Version 9.2.0.1.0. RM name = 'Oracle_XA'
    to
    ORACLE XA: Version 8.0.6.0.0. RM name = 'Oracle_XA'.
    After the upgrade.
    Any ideas why is this happening?
    Have you come across this issue after any upgrade?

  • Can't start xbmc.service since upgrade to xbmc 12.3-10

    Hi,
    I normally start xbmc via a service file and do not use a login manager, and have done successfully for some time now,
    I can no longer start xbmc.service since upgrading to xbmc 12.3-10
    The errors I receive in the journal are:
    Feb 27 10:52:20 wolverine systemd[242]: pam_nologin(login:account): conversation failed
    Feb 27 10:52:20 wolverine systemd[242]: Failed at step PAM spawning /usr/bin/xinit: Operation not permitted
    Looking at the old and new xbmc.service files, the new xbmc.service now has an additional line specifying "PamName=login"
    Not sure what I need to look at to fix this, any ideas are much appreciated.
    I am temporarily using the old xbmc.service file from the xbmc 12.3-9 package to ensure xbmc starts.
    Thanks in advance for any help.

    Thought I'd chime in here, as I'm having the same problem.  I am using the default service file provided by the xbmc package.  Commenting out PAMName=login in xbmc.service allows xbmc to start successfully on boot.  If I start xbmc.service from a normal shell prompt, it will start fine even with PAMName set.
    cat /usr/lib/systemd/system/xbmc.service
    [Unit]
    Description = Starts instance of XBMC using xinit
    After = remote-fs.target
    [Service]
    User = xbmc
    Group = xbmc
    PAMName=login
    Type = simple
    ExecStart = /usr/bin/xinit /usr/bin/dbus-launch /usr/bin/xbmc-standalone -l /run/lirc/lircd -- :0 -nolisten tcp
    Restart = on-abort
    [Install]
    WantedBy = multi-user.target
    systemctl -l status xbmc.service
    xbmc.service - Starts instance of XBMC using xinit
    Loaded: loaded (/usr/lib/systemd/system/xbmc.service; enabled)
    Active: failed (Result: exit-code) since Fri 2014-02-28 10:56:50 EST; 42min ago
    Process: 205 ExecStart=/usr/bin/xinit /usr/bin/dbus-launch /usr/bin/xbmc-standalone -l /run/lirc/lircd -- :0 -nolisten tcp (code=exited, status=224/PAM)
    Main PID: 205 (code=exited, status=224/PAM)
    CGroup: /system.slice/xbmc.service
    Feb 28 10:56:49 zbox systemd[1]: Starting Starts instance of XBMC using xinit...
    Feb 28 10:56:49 zbox systemd[1]: Started Starts instance of XBMC using xinit.
    Feb 28 10:56:50 zbox systemd[1]: xbmc.service: main process exited, code=exited, status=224/PAM
    Feb 28 10:56:50 zbox systemd[1]: Unit xbmc.service entered failed state.
    cat /etc/pam.d/login
    #%PAM-1.0
    auth required pam_securetty.so
    auth requisite pam_nologin.so
    auth include system-local-login
    account include system-local-login
    session include system-local-login

  • Can't start RoboHelp5 after I used trial of RH6

    I installed the trial version of RH6 on my computer. (Before
    doing so, I made backups of my project, in case of non
    compatibility with RH5). After the trial period I decided not to
    buy it yet and uninstalled RH6, because I couldn't find important
    differences (at least not concerning the functions I'm using) and
    because the font problem (conversion from Arial to Times, even with
    the Adobe patch and after uninstalling alle security updates for
    Office) was the same with RH6.
    Now I can't start my projects at all. When I try to start the
    RH Explorer I get a message, that the registry AppPath can't be
    read. I uninstalled both: Office and RH completely, reinstalled
    Office 2003, then RoboHelp, but the same problem is appearing.
    Even the projects I saved as backup and that I never opened
    in RH6 don't work any more.
    Any idea what I can do? (can there be hidden elements of RH6
    which are not deleted automatically, when uninstalling with the
    Software menu in my control panel?)

    On my site there is a topic about installing and
    uninstalling. In it there is reference to an Adobe topic covering a
    full uninstall which does require some registry editing. That was
    written for X5 but I think it will cover RH6. I cannot guarantee
    that though.
    Make sure you create a System Restore point before you start
    playing with the registry and only do that if you feel confident.
    If not, enlist some help from IT or a developer.

Maybe you are looking for