t eD iI N; InnoDB: End of page dump 140915 12:19:26 InnoDB: Page checksum 1570298453 (32bit_calc: 3018546506), prior-to-4.0.14-form checksum 1152805193 InnoDB: stored checksum 1570298453, prior-to-4.0.14-form stored checksum 1152805193 InnoDB: Page lsn 69 2816875854, low 4 bytes of lsn at page end 2816875854 InnoDB: Page number (if stored to page already) 4, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be an update undo log page InnoDB: Page may be an index page where index id is 18446744069414584320 140915 12:19:26 InnoDB: Assertion failure in thread 139780984702912 in file page0cur.c line 905 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 140915 12:19:26 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.
Server version: 5.5.39-MariaDB-1~saucy-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=302 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1991930 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x48000 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f214c7efdae] /usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7f214c3e1f07] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0)[0x7f214b491bb0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f214a4aef77] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f214a4b25e8] /usr/sbin/mysqld(+0x816543)[0x7f214c730543] /usr/sbin/mysqld(+0x7f9e4c)[0x7f214c713e4c] /usr/sbin/mysqld(+0x7fbea6)[0x7f214c715ea6] /usr/sbin/mysqld(+0x780253)[0x7f214c69a253] /usr/sbin/mysqld(+0x791518)[0x7f214c6ab518] /usr/sbin/mysqld(+0x77ab5b)[0x7f214c694b5b] /usr/sbin/mysqld(+0x7dc453)[0x7f214c6f6453] /usr/sbin/mysqld(+0x795b75)[0x7f214c6afb75] /usr/sbin/mysqld(+0x72d009)[0x7f214c647009] /usr/sbin/mysqld(+0x6e8b9e)[0x7f214c602b9e] /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x7f214c3e4938] /usr/sbin/mysqld(+0x38dbd5)[0x7f214c2a7bd5] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x531)[0x7f214c2acb51] /usr/sbin/mysqld(+0x2f1282)[0x7f214c20b282] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x5ca)[0x7f214c2101ca] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f214a499de5] /usr/sbin/mysqld(+0x2ec6f7)[0x7f214c2066f7] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 140915 12:19:26 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140915 12:46:04 InnoDB: Waiting for the background threads to start 140915 12:46:05 InnoDB: Waiting for the background threads to start
찾아보니, 다음 옵션을 추가하라고 한다.
innodb_purge_threads=0
mysqlcheck --all-databases 를 해본다.
InnoDB: space id 74 did not exist in memory. Retrying an open. 140915 13:24:47 InnoDB: Warning: allocated tablespace 74, old maximum was 9 .... InnoDB: space id 83 did not exist in memory. Retrying an open
다음과 같은 메시지가 나온다.
점점 골치가 아파진다. 나에겐 InnoDB 는 사치인가?
이런 에러도 보인다.
140915 20:04:43 InnoDB: Assertion failure in thread 140280661518080 in file fsp0fsp.c line 2113
저의 개발환경 구성을 이렇게 하고 있다.(사정이 있어 기존 구성된 환경을 유지하려다 보니 복잡해 보인다)
[개발서버(소스)] => 개발VM(nfs) => web-dev 외부작업환경1) 윈도우 네트워크 드라이브 -> vm (smb) 외부작업환경2) (remote) -> sftp -> smb_mount -> vm (smb)
그에 맞게 작업환경을 꾸미다보니 sftp 로 직접 붙이려니 애매한 부분이 있었다. 그래서 중간에 smb mount 해서 사용하기로 했다.
1. samba 관련 설정. /etc/samba/smb.conf (설치 부분은 생략)
[httpd] comment = working dev httpd path = /work/httpd browseable = yes hosts allow = 127.0.0.1 force user = www-data force group = www-data public = yes guest ok = yes writable = yes printable = no create mask = 0765 directory mask = 0755
[warning] /usr/bin/freemind: No java runtime was found [error] /usr/bin/freemind: Unable to find an appropriate java runtime. See java_wrappers(7) for help
fsockopen 을 쓰는 API 의 라이브러리를 사용하다가 이런 메세지를 만나게 되었다.
Warning: Call-time pass-by-reference has been deprecated - argument passed by value; If you would like to pass it by reference, modify the declaration of fsockopen(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file. However, future versions may not support this any longer. in ....
php.ini 의 allow_call_time_pass_reference 부분을 고치느냐.
API 라이브러리를 고치느냐.
10초 고민하다가, fsockopen 에서 value 를 받는 방식으로 바꿨다.
(fsockopen 에서 reference 로 받아야 하는 이유가 있나?)
웹카메라를 가지고 놀다 보니. 어떤 캠에서는 LED 가 계속 켜져 있는 상태가 되기도 한다. 볼륨조절하듯 조절가능한 것도 있기는 한데, 안되는 황당한 놈들이 있다.
생각으로는 usb port 별로 전원컨트롤 할 수 있는 방법이 있지 않을까 찾아보았다.
비슷한 것들이 있기는 한데, 완전히 차단시키지는 못하는 듯 하다.
root@ubuntu:/sys/bus/usb# lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0ac8:3332 Z-Star Microelectronics Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@ubuntu:/sys/bus/usb# echo suspend > devices/2-2/power/level
root@ubuntu:/sys/bus/usb# lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@ubuntu:/sys/bus/usb# echo on > devices/2-2/power/level
root@ubuntu:/sys/bus/usb# lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0ac8:3332 Z-Star Microelectronics Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@ubuntu:/sys/bus/usb#
위와 같이
echo suspend > /sys/bus/usb/devices/{device usb port}/power/level
처럼 값을 주면 usb 장치가 사라졌다 on 하면 다시 보인다.
그런데, 그것이 완전히 전원을 차단하는 것은 아니다. 작동상태정도만 조절하는 듯 하다.(메인 보드 마다 다를 수 있을지는 모르겠다)
또 다른 방법도 있다고 하는데.
echo "0" > /sys/bus/usb/devices/{device usb port}/power/state
다음과 같은 에러가 난다.
bash: devices/2-2/power/state: No such file or directory
가상장치같은 개념이라 없는 파일(state)을 만들 수는 없나 보다.