Hot answers tagged ubuntu
7
This part is unusual:
ORACLE_HOME=/u01/app/oracle/product/11.2.0/xe/
This needs to be char-by-char identical every time. I see it ends with a slash here, which is non-standard, and I suspect that you've added it by mistake. Adding a slash will result in "ORACLE not available" in so-called bequeath sqlplus, I've just experimented on my system. Try again ...
7
Are you running from the 10gen repository or from the default Debian/Ubuntu repo? I recommend using the official 10gen repository.
Check this link out - [10gen MongoDB How-To Install on Ubuntu:] http://docs.mongodb.org/manual/tutorial/install-mongodb-on-debian-or-ubuntu-linux/. It is best to uninstall the previous mongodb installation prior to this change, ...
6
The line in your netstat report shows that the database is only listening on localhost:5432 (127.0.0.1) for incoming tcp conections.
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 3561/postgres
So it can only accept local tcp connections regardless of what ...
4
UPDATE: it looks like this is a bug in the Debian/Ubuntu packaging of PostgreSQL, where the init scripts - extremely unsafely - kill -9 the postmaster and remove postmaster.pid. See this post on pgsql-general.
See:
https://bugs.launchpad.net/debian/+source/postgresql-common/+bug/1042556
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686060
...
4
You can turn off (and on) the paging in psql:
\pset pager [on|off]
If you don't specify on or off, the command will toggle the setting. (More on \pset in the documentation.)
In the shell, you can even set the pager you want to use:
PAGER=/usr/bin/less
If you start psql after this, less will be your pager.
3
Ubuntu or Debian can run multiple instances of PostgreSQL and provide a specific way to autostart/stop/start each cluster.
There should be a file named start.conf inside /etc/postgresql/9.2/main (or more generally /etc/postgresql/<version>/<clustername>) with these self-explanatory contents:
# Automatic startup configuration
# auto: automatically ...
3
Your databases will remain untouched (though of course I can't be liable :) ).
The reason are are being asked for a password could be:
Your new Ubuntu version uses a newer version of MySQL (it does). It needs root password so as to run the mysql_upgrade utility, which upgrades internal mysql schema to fit new version
You new installation includes new ...
3
While I wait for your logs (see comments), there are two common causes for this:
Bad permissions on the log file, or other bad permissions in the data path. Make sure you chown/chmod everything under the /media/newdrive/data folder. Something similar to this:
sudo chown -R mongodb:mongodb /media/newdrive/data
Then make sure your other mongod instance ...
3
To clear the WAL files, see pg_resetxlog.
The data directory on Ubuntu 12 should be /var/lib/postgresql/9.1/main
Note that pg_resetxlog is located in /usr/lib/postgresql/9.1/bin, not in /usr/bin, so it's not necessarily in $PATH. Also it should be run as the postgres user.
To clear and recreate the entire cluster if you don't care about the data, run:
...
3
Unfortunately, yes, you'll need to reduce the size of your root LV.
(You could reduce the size of swap, too, but that's already a fairly small volume)
Even if you can use that 4MB, a snapshot of your root volume will become invalid quite quickly when LVM runs out of "free" disk space.
You get prompted with a text box asking how much of your disk to use ...
2
On MySQL Version 5.5 the NFORMATION_SCHEMA directory/folder exists; I am assuming it does on other versions. It's not controlled in the setting of my.ini or my.cnf as datadir=whatever; it appears to be predefined in the install path of MySQL and is read when MySQL first loads on startup.
There is no my.ini or my.cnf setting for placing the location of ...
2
There error is telling ... The problem is that you ran initdb as your local login, but I'm pretty that your login (username) doesn't have access to /var/run/postgresql. If you have a clean install, may I recommend that you remove the data directory and start all over, this time by su-ing into the postgres account:
username@jupiter:~$ sudo su - postgres
...
2
OBSERVATION #1
Since your buffer pool is 6G (6144M), the innodb_log_file_size should be 1536M (25% of 6G)
OBSERVATION #2
You have sync_binlog set to 1. This provides the safest ACID compliant setup. It can also slow things down dramatically. You say it seems as though its writing each row 1 at a time to disk. That's the case because each completed DML ...
2
I think the permissions are correct because otherwise you wouldn't have gotten here.
My guess is that a modification you have made has caused the problem. This is particularly the case given that it is a segmentation fault. What you really need to do is look at the call stack at the time the core was dumped and see if you can isolate where in the code ...
2
First try connecting to the database as the postgres user
jay@machine$ sudo su postgres
postgres@machine$ psql
Then create a new user, and why not create a database if you haven't already
postgres=# CREATE USER jay WITH password 'donttell';
postgres=# CREATE DATABASE gis;
postgres=# \q
You should now be able to connect as yourself
jay@machine$ psql ...
2
Well, I have some advice for you.
Given https://help.ubuntu.com/12.04/serverguide/mysql.html,
As of Ubuntu 12.04, MySQL 5.5 is installed by default
Go with the 5.5.x version they supply, and update accordingly.
If you don't want to do that and really want 5.5.29 for a specific reason, go for mysql-5.5.29-debian6.0-x86_64.deb as Ubuntu was derived ...
1
Look at this line
[OK] Key buffer size / total MyISAM indexes: 250.0G/131.6G
The sum of all your MyISAM indexes is 131.6G
You should lower key_buffer_size to 140G. This will give back 110G.
I have a little suggestion for you. You may want to consider using a dedicate keycache for each large table. See my Nov 16, 2012 post Cache all mysql table
Look at ...
1
It looks like something went wrong when you upgraded. You have to check that the port and listen_addresses are correct. Perhaps the listen_address changed and the instance isn't listening on the host anymore?
The reason that pg_dump and the other tools are still working is probably because they're connecting over the unix socket instead over TCP/IP. ...
1
Just don't leave the Database field empty in the connection dialog.
When left empty, it will attempt to connect to a database named after your OS login name, which probably doesn't exist in your case.
The Host field should be left empty to use a Unix domain socket connection, as hinted by the snippet of your pg_hba.conf shown in the question.
When you put ...
1
I'm not sure about your package management issues but wanted to point out that the docs Say that you should completely reload your data using mysqldump when upgrading from a previous minor version. So once you have your complete mysqldump w/ --all-databases --events --routines, be sure to import that into the new binaries.
1
initdb and the server process itself must be run as the same OS user which owns the data directory. Don't forget to set permissions for that directory to only allow that user access (chmod 700).
Regarding the segmentation fault -- can you cause it with an unmodified version of PostgreSQL, or is this perhaps a result of bug in some customization you've ...
1
You installed a version of readline different than the one already installed by ubuntu. You may probably safely remove it, since postgresql will get the other one.
BTW, why do you recompiled postgresql on ubuntu? If you don't like to version provided in your ubuntu release, just point your apt to http://pgapt.debian.net/ and get the version you like more.
1
It appears you have an 8.4 database that isn't managed by pg_wrapper, and have installed 9.1 from Ubuntu packages and allowed it to create a pg_wrapper managed cluster in the default location, which isn't where you want the DB.
pg_upgradecluster from pg_wrapper isn't suitable for this, since you hand-initdb'd the old cluster.
If the 9.1 cluster doesn't ...
1
Don't know about 2) and 3) (I don't use Ubuntu).
But to migrate the data from 8.4 to 9.1 pg_dump.
Assuming that that 8.4 runs on port 5432 and 9.1 runs on port 5433 something like the following will copy all the data from 8.4 to 9.1:
/usr/lib/postgresql/9.1/bin/pg_dump -p 5432 -U -c -C postgres my_db | /usr/lib/postgresql/9.1/bin/psql -p 5433
This ...
1
You may find this surprising but MySQL 5.5 can be configured to access multiple cores for InnoDB. The features are not on by default. In fact, there are occasions when older versions of MySQL run faster "out-of-the-box" than MySQL 5.5.
I have written posts about this before:
Jun 19, 2011 : How do I properly perform a MySQL bake-off?
Oct 05, 2011 : Query ...
1
From this listing it looks like there is a package named postgresql-9.2-postgis2. You may have to add a new apt repository to the existing ones. In this, you can find help here.
1
Assuming less is used as the pager, you can turn off this screen-clearing feature which indeed is annoying within psql. Use the -X option:
-X or --no-init
Disables sending the termcap initialization and deinitialization
strings to the terminal. This is sometimes desirable if the
deinitialization string does something ...
1
If the existing main is the default cluster that was created with your installation you can just drop it. Use the tool provided by your installation:
pg_dropcluster --stop 9.1 main
More info: man pg_dropcluster
There is nothing special about the main cluster. It's just an cluster like any other which happens to be the default in your installation.
If ...
1
The upgrade of the server itself should be a piece of cake, even for the casual admin.
However...
There are many, many changes between 4.x and 5.x. I would not expect to be able to import a v4-dump into a v5-server straight out-of-the-box.
Be prepared for a strong head ache during data migration. Also, prepare your devs for significant (I'm tempted to ...
Only top voted, non community-wiki answers of a minimum length are eligible
