Latest OS X Server update removed my device_management database?

Question

Level 1

0 points

Latest OS X Server update removed my device_management database?

Hello,

I recently updated my OS X Mountain Lion Server version to 2.2 and I can't seem to find my device_management database in the postgres database?

I've been backing up my database and now can no longer find it. When I start up profile manager it definitely starts up and has data in it? Is there some other location for the database now? WHAT Happened?

Any ideas would be helpful...

I currently see this:

-----------+-----------+----------+---------+-------+-------------------------

postgres | _postgres | UTF8 | C | C |

template0 | _postgres | UTF8 | C | C | =c/_postgres +

template1 | _postgres | UTF8 | C | C | _postgres=CTc/_postgres+

where on my test Profile Manager machine with the same update I see this:

ostgres=# \l

List of databases

------------------+-----------+----------+---------+-------+-------------------- -----

device_inventory | _postgres | UTF8 | C | C |

postgres | _postgres | UTF8 | C | C |

template0 | _postgres | UTF8 | C | C | =c/_postgres +

template1 | _postgres | UTF8 | C | C | _postgres=CTc/_postgres+

test | _postgres | UTF8 | C | C |

OS X Mountain Lion (10.8.2)

Posted on Dec 11, 2012 4:53 PM

Reply

Answer 1

toddatkuapay Author

Level 1

0 points

Dec 11, 2012 5:16 PM in response to toddatkuapay

Ok well I've found the database but can not find out how to connect and retrieve the data from it. I need to backup my database and then use the data for an inhouse inventory database...

Any help appreciated.

Reply

Answer 2

toddatkuapay Author

Level 1

0 points

Dec 12, 2012 8:47 AM in response to toddatkuapay

So there are now 2 postgres servers running and I can't connect to the /Library/Server/PostgreSQL For Server Services...

The reason for this is that psql is pointing to the original location of the socket directory. By simply shutting down the 2nd instance of the Postgres database and linking the running socket in the original socket directory - you can connect to the /Library/Server/PostgreSQL for Server Services instance.

Simply put:

1.) launchctl remove org.postgresql.postgres

2.) launchctl list | grep postgre

3.) ln -s /Library/Server/PostgreSQL\ For\ Server\ Services/Socket/.s.PGSQL.5432 /var/pgsql_socket/.s.PGSQL.5432

And you can connect to the database you need by:

psql -U _postgres -d postgres

Reply

Answer 3

Dec 14, 2012 8:32 AM in response to toddatkuapay

You can also use:

psql -U _postgres -h /Library/Server/PostgreSQL\ For\ Server\ Services/Socket/ -lt

Reply

Answer 4

toddatkuapay Author

Level 1

0 points

Dec 14, 2012 8:38 AM in response to Peter Jurg2

Peter - thank you! That's a more elegant solution...

Reply