Home / user-107794

Linus Oleander's questions

Martin Hope
Linus Oleander
Asked: 2013-12-23 16:07:08 +0800 CST
  • 6

I'm trying to install postgresql 9.3 in my ubuntu lucid machine. The problem is that I'm getting this error when running apt-get install postgresql-9.3

=> apt-get install postgresql-9.3
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  postgresql-client-9.3
Suggested packages:
  oidentd ident-server locales-all postgresql-doc-9.3
The following NEW packages will be installed:
  postgresql-9.3 postgresql-client-9.3
0 upgraded, 2 newly installed, 0 to remove and 700 not upgraded.
Need to get 8,944 kB of archives.
After this operation, 23.6 MB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://apt.postgresql.org/pub/repos/apt/ lucid-pgdg/main postgresql-client-9.3 amd64 9.3.2-1.pgdg10.4+1 [2,186 kB]
Get:2 http://apt.postgresql.org/pub/repos/apt/ lucid-pgdg/main postgresql-9.3 amd64 9.3.2-1.pgdg10.4+1 [6,758 kB]
Fetched 8,944 kB in 6s (1,294 kB/s)
Selecting previously unselected package postgresql-client-9.3.
(Reading database ... 48797 files and directories currently installed.)
Unpacking postgresql-client-9.3 (from .../postgresql-client-9.3_9.3.2-1.pgdg10.4+1_amd64.deb) ...
Selecting previously unselected package postgresql-9.3.
Unpacking postgresql-9.3 (from .../postgresql-9.3_9.3.2-1.pgdg10.4+1_amd64.deb) ...
Setting up postgresql-client-9.3 (9.3.2-1.pgdg10.4+1) ...
update-alternatives: error: alternative pg_basebackup.1.gz can't be slave of psql.1.gz: it is a slave of postmaster.1.gz
dpkg: error processing postgresql-client-9.3 (--configure):
 subprocess installed post-installation script returned error exit status 2
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of postgresql-9.3:
 postgresql-9.3 depends on postgresql-client-9.3; however:
  Package postgresql-client-9.3 is not configured yet.
dpkg: error processing postgresql-9.3 (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              Errors were encountered while processing:
 postgresql-client-9.3
 postgresql-9.3
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've been searching on google for two hours without solving the problem. Why is this happening and how could I solve it?

ubuntu
Martin Hope
Linus Oleander
Asked: 2012-12-06 10:17:53 +0800 CST
  • 1

I've a bit of a problem with MySQL crashing once every ~24h.

This is the error log.

121205  9:42:49 [Note] Plugin 'FEDERATED' is disabled.
121205  9:42:49 InnoDB: The InnoDB memory heap is disabled
121205  9:42:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121205  9:42:49 InnoDB: Compressed tables use zlib 1.2.3.4
121205  9:42:49 InnoDB: Initializing buffer pool, size = 512.0M
121205  9:42:49 InnoDB: Completed initialization of buffer pool
121205  9:42:49 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
121205  9:42:49  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
121205  9:42:49  InnoDB: Waiting for the background threads to start
121205  9:42:50 InnoDB: 1.1.8 started; log sequence number 2449055943
121205  9:42:50 [Note] Event Scheduler: Loaded 0 events
121205  9:42:50 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.22-0ubuntu1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 49827  (Ubuntu)
121205  9:42:51 [ERROR] /usr/sbin/mysqld: Table './application/songs' is marked as crashed and should be repaired
121205  9:42:51 [Warning] Checking table:   './application/songs'
121205  9:42:51 [ERROR] /usr/sbin/mysqld: Table './application/artists' is marked as crashed and should be repaired
121205  9:42:51 [Warning] Checking table:   './application/artists'
121205  9:42:52 [ERROR] /usr/sbin/mysqld: Table './application/channels' is marked as crashed and should be repaired
121205  9:42:52 [Warning] Checking table:   './application/channels'
121205 10:50:57 [Note] Plugin 'FEDERATED' is disabled.
121205 10:50:57 InnoDB: The InnoDB memory heap is disabled
121205 10:50:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121205 10:50:57 InnoDB: Compressed tables use zlib 1.2.3.4
121205 10:50:57 InnoDB: Initializing buffer pool, size = 512.0M
121205 10:50:57 InnoDB: Completed initialization of buffer pool
121205 10:50:57 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
121205 10:50:57  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
121205 10:50:57  InnoDB: Waiting for the background threads to start
121205 10:50:58 InnoDB: 1.1.8 started; log sequence number 2449882518
121205 10:50:58 [Note] Event Scheduler: Loaded 0 events
121205 10:50:58 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.22-0ubuntu1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 49827  (Ubuntu)
121205 10:50:59 [ERROR] /usr/sbin/mysqld: Table './application/artists' is marked as crashed and should be repaired
121205 10:50:59 [Warning] Checking table:   './application/artists'
121205 10:50:59 [ERROR] /usr/sbin/mysqld: Table './application/songs' is marked as crashed and should be repaired
121205 10:50:59 [Warning] Checking table:   './application/songs'
121205 10:51:00 [ERROR] /usr/sbin/mysqld: Table './application/channels' is marked as crashed and should be repaired
121205 10:51:00 [Warning] Checking table:   './application/channels'

It crashed right after 10:51 (like in the log).

Why is this happening?

My current system

  • MySQL Ver 14.14 Distrib 5.5.22, for debian-linux-gnu (x86_64) using readline 6.2
  • Ubuntu 12.04 LTS
ubuntu
Martin Hope
Linus Oleander
Asked: 2012-11-16 14:26:23 +0800 CST
  • 1

I restarted my elasticsearch instance 5 days ago and I haven't manage to start it since then.

I get no output in the log file /var/log/elasticsearch/ nor does the elasticsearch binary print any information when running at using elasticsearch -f.

I once manage to get this output.

[2012-11-15 22:51:18,427][INFO ][node                     ] [Piper] {0.19.11}[29584]: initializing ...
[2012-11-15 22:51:18,433][INFO ][plugins                  ] [Piper] loaded [], sites []

Running curl http://localhost:9200 resulted in curl: (7) couldn't connect to host.

I've tried increasing the memory from 3gb to 10gb, but that didn't make any diffrence.

Running /etc/init.d/elasticsearch start takes 30 seconds. ps aux | grep elasticsearch results in this output.

/usr/local/share/elasticsearch/bin/service/exec/elasticsearch-linux-x86-64 /usr/local/share/elasticsearch/bin/service/elasticsearch.conf wrapper.syslog.ident=elasticsearch wrapper.pidfile=/usr/local/share/elasticsearch/bin/service/./elasticsearch.pid wrapper.name=elasticsearch wrapper.displayname=ElasticSearch wrapper.daemonize=TRUE wrapper.statusfile=/usr/local/share/elasticsearch/bin/service/./elasticsearch.status wrapper.java.statusfile=/usr/local/share/elasticsearch/bin/service/./elasticsearch.java.status wrapper.script.version=3.5.14

/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java -Delasticsearch-service -Des.path.home=/usr/local/share/elasticsearch -Xss256k -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.awt.headless=true -Xms1024m -Xmx1024m -Djava.library.path=/usr/local/share/elasticsearch/bin/service/lib -classpath /usr/local/share/elasticsearch/bin/service/lib/wrapper.jar:/usr/local/share/elasticsearch/lib/elasticsearch-0.19.11.jar:/usr/local/share/elasticsearch/lib/elasticsearch-0.19.11.jar:/usr/local/share/elasticsearch/lib/jna-3.3.0.jar:/usr/local/share/elasticsearch/lib/log4j-1.2.17.jar:/usr/local/share/elasticsearch/lib/lucene-analyzers-3.6.1.jar:/usr/local/share/elasticsearch/lib/lucene-core-3.6.1.jar:/usr/local/share/elasticsearch/lib/lucene-highlighter-3.6.1.jar:/usr/local/share/elasticsearch/lib/lucene-memory-3.6.1.jar:/usr/local/share/elasticsearch/lib/lucene-queries-3.6.1.jar:/usr/local/share/elasticsearch/lib/snappy-java-1.0.4.1.jar:/usr/local/share/elasticsearch/lib/sigar/sigar-1.6.4.jar -Dwrapper.key=k7r81VpK3_Bb3N_5 -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.disable_console_input=TRUE -Dwrapper.pid=23888 -Dwrapper.version=3.5.14 -Dwrapper.native_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp org.elasticsearch.bootstrap.ElasticSearchF

My current system:

  • ElasticSearch Version: 0.19.11, JVM: 23.2-b09
  • Ubuntu 12.04 LTS
  • OpenJDK 64-Bit Server VM - 1.7.0_09

I've tried re-installing elasticsearch, removing old directories, reinstalling java and restarting the server.

Why can't I get it to start?

ubuntu
Martin Hope
Linus Oleander
Asked: 2012-02-05 15:29:52 +0800 CST
  • 6

I'm having some strange problem with the clock on my server – it's about 10% faster than normal.

The problem started 2 days ago and I've not done anything special with the server.

I tried to turn of the ntp update by stopping the ntpd daemon.

It looks like the hardware clock is disabled.

→ sudo hwclock --show
select() to /dev/rtc to wait for clock tick timed out
  • Server has not been restarted for 100+ days
  • Linus distro is Debian squeeze/sid
  • ntpd daemon is turned of
  • Server is a VPS, non of the other customers have had any problem
  • I've not changed anything related to the clock in terms of software
  • Running sudo date -s "Sun Feb 5 00:30:15 CET 2012" or sudo ntpdate -b prrr.se, fixes the problem temporarily

I tried to mesure the offset by using ntpdate -b prrr.se. This is the result

After 5 sec

→ sudo ntpdate -b prrr.se
 5 Feb 00:19:54 ntpdate[24137]: step time server 178.78.255.254 offset -1.179405 sec

After 10 sec

→ sudo ntpdate -b prrr.se
 5 Feb 00:20:04 ntpdate[24142]: step time server 178.78.255.254 offset -2.480711 sec

After 20 sec

→ sudo ntpdate -b prrr.se
 5 Feb 00:20:24 ntpdate[24149]: step time server 178.78.255.254 offset -4.680055 sec

Can anyone explain to me why this is happening and what might be the solution?

linux time debian clock-synchronization
Martin Hope
Linus Oleander
Asked: 2012-01-22 02:53:16 +0800 CST
  • 3

I'm having some problem with my Debian 2.6.38-3 server which **crashes* once every 3 month, but I can't figure out why.

According to Pingdom the site died around 4 AM, but none of the logs I've looked at contains any info about any kind of error.

This is the log files I've looked through:

  • /var/log/messages
  • /var/log/syslog
  • /var/log/debug
  • /var/log/kern.log

According to the given logs there is noting wrong. Here is an example from /var/log/messages.

Jan 21 04:01:46 debian god[1195]: app still alive after 10s; sent SIGKILL

Jan 21 11:18:20 debian kernel: imklog 3.18.6, log source = /proc/kmsg started.

Any ideas what logs may contain the info I'm looking for?

**crashes as in does not respond to anything. Screen turns black, doesn't responds to web requests and I can't access it using SSH.*

linux logging debian