Upgrade verkar inte fungera som avsett.

http://automagucally.weebly.com

Moderators: davka003, Telldus

Post Reply
jimmy927
Posts: 27
Joined: Thu Jan 18, 2018 11:08 am
Location: Stockholm
Contact:

Upgrade verkar inte fungera som avsett.

Post by jimmy927 » Thu Jan 18, 2018 11:08 am

Om jag kör upgrade manuellt via scriptet på consollen så händer detta:

Code: Select all

root@raspberrypi:/var/lib/mysql# date ; bash -x /home/pi/source/automagically/update.sh
Sat Feb 15 19:56:30 UTC 2014
+ cd /home/pi/source/automagically
+ git pull
Already up-to-date.
+ cd /home/pi/source/automagically/site
+ sudo /etc/init.d/apache2 stop
[....] Stopping web server: apache2apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
[Sat Feb 15 19:56:34 2014] [warn] NameVirtualHost *:80 has no VirtualHosts
. ok
+ sudo /etc/init.d/automagically stop
pidfile /var/run/automagically.pid does not exist. Daemon not running?
+ sudo /etc/init.d/mysql restart
[ ok ] Stopping MySQL database server: mysqld.
[ ok ] Starting MySQL database server: mysqld ..
[info] Checking for tables which need an upgrade, are corrupt or were
not closed cleanly..
+ python manage.py migrate core
Running migrations for core:
- Nothing to migrate.
 - Loading initial data for core.
Installed 16 object(s) from 1 fixture(s)
+ python manage.py migrate signals
Running migrations for signals:
- Nothing to migrate.
 - Loading initial data for signals.
Installed 0 object(s) from 0 fixture(s)
+ python manage.py migrate settings
Running migrations for settings:
- Nothing to migrate.
 - Loading initial data for settings.
Installed 0 object(s) from 0 fixture(s)
+ python manage.py migrate remote
Running migrations for remote:
- Nothing to migrate.
 - Loading initial data for remote.
Installed 3 object(s) from 1 fixture(s)
+ mysql --user root --password=raspberry automagically
+ python manage.py collectstatic --noinput

0 static files copied, 99 unmodified.
+ echo ' '
+ chmod 666 plugins/signaldebug.txt
root@raspberrypi:/var/lib/mysql# echo $?
0
root@raspberrypi:/var/lib/mysql#

I daemonlog så der jag detta:

Code: Select all

Feb 15 19:56:40 raspberrypi mysqld: 140215 19:56:40 [Note] /usr/sbin/mysqld: Normal shutdown
Feb 15 19:56:40 raspberrypi mysqld:
Feb 15 19:56:40 raspberrypi mysqld: 140215 19:56:40 [Note] Event Scheduler: Purging the queue. 0 events
Feb 15 19:56:40 raspberrypi mysqld: 140215 19:56:40 [Note] /usr/sbin/mysqld: Shutdown complete
Feb 15 19:56:40 raspberrypi mysqld:
Feb 15 19:56:41 raspberrypi mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Feb 15 19:56:45 raspberrypi mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] An old style --language value with language specific part detected: /usr/share/mysql/english/
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Use --lc-messages-dir without language specific part instead.
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [Note] Plugin 'FEDERATED' is disabled.
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [Note] Plugin 'InnoDB' is disabled.
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [Note] Server socket created on IP: '0.0.0.0'.
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/events_waits_current.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/events_waits_history.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/events_waits_history_long.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/setup_consumers.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/setup_instruments.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/setup_timers.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/performance_timers.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/threads.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/events_waits_summary_by_thread_by_event_name.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/events_waits_summary_by_instance.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/events_waits_summary_global_by_event_name.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/file_summary_by_event_name.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/file_summary_by_instance.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/mutex_instances.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/rwlock_instances.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/cond_instances.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] /usr/sbin/mysqld: Can't find file: './performance_schema/file_instances.frm' (errno: 13)
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [Note] Event Scheduler: Loaded 0 events
Feb 15 19:56:45 raspberrypi mysqld: 140215 19:56:45 [Note] /usr/sbin/mysqld: ready for connections.
Feb 15 19:56:45 raspberrypi mysqld: Version: '5.5.31-0+wheezy1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
Feb 15 19:56:46 raspberrypi /etc/mysql/debian-start[5774]: Upgrading MySQL tables if necessary.
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: Looking for 'mysql' as: /usr/bin/mysql
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock'
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock'
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.auth_group                           OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.auth_group_permissions               OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.auth_permission                      OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.auth_user                            OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.auth_user_groups                     OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.auth_user_user_permissions           OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.celery_taskmeta                      OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.celery_tasksetmeta                   OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_command                         OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_currentvalue                    OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_datafetcher                     OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_device                          OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_event                           OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_globalvariable                  OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_groupdevice                     OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_groupdevice_subDevices          OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_preset                          OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_presetentry                     OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_rawtellstickdevice              OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_rawtellstickdevice_controllingSameDeviceAs OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_scheduledevent                  OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_sendsignaldevice                OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_threshold                       OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_timerdevice                     OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_valuehistory                    OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_valuehistorymem                 OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_variabledelayedcommand          OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.core_woldevice                       OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.django_admin_log                     OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.django_content_type                  OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.django_session                       OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.django_site                          OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.djcelery_crontabschedule             OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.djcelery_intervalschedule            OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.djcelery_periodictask                OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.djcelery_periodictasks               OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.djcelery_taskstate                   OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.djcelery_workerstate                 OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_dimdev                        OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_genericcontent                OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_heading                       OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_link                          OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_onoffdev                      OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_page                          OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_remote                        OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_singledevcmd                  OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_theme                         OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_variablevalue                 OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.remote_widget                        OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.settings_group                       OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.settings_settingsvalue               OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.signals_devicecommand                OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.signals_findrepeat                   OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.signals_handler                      OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.signals_storeglobalvariable          OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.signals_transform                    OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: automagically.south_migrationhistory               OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: mysql.columns_priv                                 OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: mysql.db                                           OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: mysql.event                                        OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: mysql.func                                         OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: mysql.general_log                                  OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: mysql.help_category                                OK
Feb 15 19:56:47 raspberrypi /etc/mysql/debian-start[5778]: mysql.help_keyword                                 OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.help_relation                                OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.help_topic                                   OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.host                                         OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.ndb_binlog_index                             OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.plugin                                       OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.proc                                         OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.procs_priv                                   OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.proxies_priv                                 OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.servers                                      OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.slow_log                                     OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.tables_priv                                  OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.time_zone                                    OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.time_zone_leap_second                        OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.time_zone_name                               OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.time_zone_transition                         OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.time_zone_transition_type                    OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: mysql.user                                         OK
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: Running 'mysql_fix_privilege_tables'...
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1007 (HY000) at line 160: Can't create database 'performance_schema'; database exists
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 183: Can't create table 'cond_instances' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 213: Can't create table 'events_waits_current' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 227: Can't create table 'events_waits_history' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 241: Can't create table 'events_waits_history_long' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 262: Can't create table 'events_waits_summary_by_instance' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 283: Can't create table 'events_waits_summary_by_thread_by_event_name' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 303: Can't create table 'events_waits_summary_global_by_event_name' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 320: Can't create table 'file_instances' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 339: Can't create table 'file_summary_by_event_name' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 359: Can't create table 'file_summary_by_instance' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 376: Can't create table 'mutex_instances' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 394: Can't create table 'performance_timers' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 412: Can't create table 'rwlock_instances' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 428: Can't create table 'setup_consumers' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 445: Can't create table 'setup_instruments' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 461: Can't create table 'setup_timers' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: ERROR 1005 (HY000) at line 478: Can't create table 'threads' (errno: 13)
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5778]: FATAL ERROR: Upgrade failed
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5802]: Checking for insecure root accounts.
Feb 15 19:56:51 raspberrypi /etc/mysql/debian-start[5807]: Triggering myisam-recover for all MyISAM tables

Nån som förstår vad som är trasigt ?

Systemet har aldrig nånsin funkat.
Det är en helt färsk image som postades på Bloggen tidigare.
Detta är mitt andra försök eftersom jag stekte min databas första gången.

KHolm
Posts: 163
Joined: Thu Jan 18, 2018 11:08 am

Re: Upgrade verkar inte fungera som avsett.

Post by KHolm » Thu Jan 18, 2018 11:08 am

Hi,

Don't know what is wrong with that, but here comes the step I perform/performed to get my system working (after my last crash without a proper backup done).

1. Create a SD card from image using win32diskimager
http://bit.ly/IrG1pi

2. Check that Automagically is running by pointing your browser to it.
(I usually login at the pi and run the "top" command to see what is happening at this point)

3. Expand file system and set timezone, language and etc.

Code: Select all

$ raspi-config
3. Update the system

Code: Select all

$ cd ~/source/automagically/
$ sudo ./update.sh
$ sudo shutdown -r now
4. When the system has booted, Automagically should be up and running. Test by pointing your browser to it.

5. Enter your settings (/admin/settings/settingsvalue/)
Start with general options and disable stuff like hdmi-cec, tellduslive, 1wire). Leave Timezone to "Europe/Stockholm" if you are in Sweden.
Long/lat you can easily get from maps.google.com

5. Remove all core settings that comes with original image through the web interface (/admin/core/)
(Global Variables, Raw Tellstick Devices, Variable delayed commands, etc.)

6. Remove all signal handlers that comes with original image through the web interface (/admin/signals/)
Check each item, remove what's there

7. [Optional] Cleanse the /etc/tellstick.conf from old "crap"

Code: Select all

$ sudo /etc/init.d/telldusd stop
$ sudo nano /etc/tellstick.conf
$ sudo /etc/init.d/telldusd start
The only thing that should be left in there is:

Code: Select all

user = "nobody"
group = "plugdev"
deviceNode = "/dev/tellstick"
ignoreControllerConfirmation = "false"
Now your have a clean fresh system to start building from.

/Marcus

jimmy927
Posts: 27
Joined: Thu Jan 18, 2018 11:08 am
Location: Stockholm
Contact:

Re: Upgrade verkar inte fungera som avsett.

Post by jimmy927 » Thu Jan 18, 2018 11:08 am

I think what i have done should really be equivalent.
And i would really know what is making my migrations break.

If you run your upgrade.sh,

does it say ?

Code: Select all

[info] Checking for tables which need an upgrade, are corrupt or were
not closed cleanly..
maybe this is normal at this point ?
i mean, the www-interface kinda works.

KHolm
Posts: 163
Joined: Thu Jan 18, 2018 11:08 am

Re: Upgrade verkar inte fungera som avsett.

Post by KHolm » Thu Jan 18, 2018 11:08 am

jimmy927 wrote: does it say ?
I recall having seen that message from time to time, yes.

What looks odd in your trace above is this:

Code: Select all

+ sudo /etc/init.d/automagically stop
pidfile /var/run/automagically.pid does not exist. Daemon not running?
That does not look healthy to me. Looks like some permission problems somewhere. Try to start it manually:

Code: Select all

$ sudo /etc/init.d/automagically start
I would also start to look if the tellstick works with the Pi as it should. Manually update your /etc/tellstick.conf and add a device, then use tdtool and see if you can control that device. Yes, it's a pain but that's how I would go about it.

One thing I had serious issues with was when I had left signaltrace on. After a few hours the system becomes very, very slow - and barely works. At this point it's hard to even stop the signal trace. What fixed it for me was:

Code: Select all

$ sudo /etc/init.d/automagically stop
$ sudo rm ~/source/automagically/site/plugins/signaldebug.txt
$ sudo /etc/init.d/automagically start
Next is to go hard-core, use with care:

Code: Select all

$ sudo /etc/init.d/automagically stop
$ cd ~/source/automagically/daemon/
$ sudo python main.py
At this point, you might see some errors while starting the daemon.
It's a bit tricky to stop it since it runs multiple threads. I found it easiest to put it into background an kill it.

Code: Select all

Ctrl-Z
$ bg
$ ps -edf | grep main.py
(Look for the PID for sudo python main.py)
$ sudo kill XXX (The PID for sudo python main.py)
Another hard-core way to find traces is this:

Code: Select all

$ cd ~/source/automagically/site
$ ./test.sh
Point your browser to http://192.168.0.,xxx:8100 and watch the output in the console; you might see errors there.

/Marcus
ps.
Looks like there is a need for a new image to be uploaded somewhere. I'll see if I can find time to do that...

KHolm
Posts: 163
Joined: Thu Jan 18, 2018 11:08 am

Re: Upgrade verkar inte fungera som avsett.

Post by KHolm » Thu Jan 18, 2018 11:08 am

KHolm wrote:I'll see if I can find time to do that...
Well, now I have the image - but it was created from a 16Gb SD card so I have nowhere to store it since it's quite big; and I guess most have smaller SD cards anyway so it'll not be possible to use. :(

Anyone interested in this (way too large) image, use the attached torrent. It comes with fully updated Linux and Automagically up-to-date with some cleansing done. I'll leave it up for at least a couple of weeks. Let me know if works, have not been able to test to download it...

/Marcus
Attachments
automagically_2014_01_16.torrent
(24.42 KiB) Downloaded 370 times

Trevis
Posts: 1
Joined: Thu Jan 18, 2018 11:08 am

Re: Upgrade verkar inte fungera som avsett.

Post by Trevis » Thu Jan 18, 2018 11:08 am

Hej! Vi har en tryckknapp från Jula (Proove) som vi har som enhet 12.bsh för att växla mellan home/away. När vi trycker knappen ON så är vi home, annars away - som i koden du angav. Problemet är att reaktionen tar väldigt lång tid, nästan en minut tills ev. lampor släcks. Telldus center svarar med en gång men Nexahome tar nästan en minut på sig. Kan man snabba upp detta?
We are the leading the world in providing best ccie mobile lab gre and 70-483 prep solutions. Our incredible offers for 400-051 and www.kumc.edu gedare accessible at reasonable prices; our Florida National University is very rare in IT world.

Post Reply