Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I need to install Chef, but it must use not PostgreSQL that come with the package, I want to use MongoDB.
So i have several questions:
How I understood it, Postgres is installed when I perform $ sudo chef-server-ctl reconfigure.
How do I exclude installing on Postgres from chef server without breaking the install off other needed components? Or I just install, run reconfigure and than redirect Chef Server to use MongoDB, if so, how can I get chef starting to use mongoDB?
It was only a little more than a year ago Opscode decided to move from CouchDB to PostgreSQL. CouchDB shared many similarities with MongoDB. Even if there's a particular compelling reason you'd like Chef server to run on MongoDB, I don't think the current framework would support it. Read more here http://www.getchef.com/blog/2013/02/15/the-making-of-erchef-the-chef-11-server/
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have a cluster of PostgreSQL nodes using streaming replication and running on RHEL 7. I plan to add new nodes running on RHEL 8, still using the same PostgreSQL version (12.7). Is mixing OS versions in a cluster a problem?
In general, streaming replication only works between the same OS and OS version.
While replicating between RHEL 7 and RHEL 8 might technically work, you might run into sever problems, e.g. because of different locale data which can lead to incorrect query results on the standby server.
I would not risk this. You should keep all servers at the same OS versions and patch level.
Logical replication on the other hand can be used to replicate between different operating systems (e.g. even from Linux to Windows). But that will require more setup and isn't really suitable if you want to replicate many databases that contain many schemas.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I have followed every step as given here. I installed all the servers and libraries but when I set the PostgreSQL server it hangs stating the follows on the terminal
LOG: database system was shut down at 2014-01-22 01:53:52 UTC
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
What to do?
I assume you're referring to these lines:
Finally, start up the server.
$ sudo -u postgres postgres -D /usr/local/pgsql/data
If so, that starts the PostgreSQL server in blocking mode. It is running. It won't exit until told to, and that terminal won't return. It sounds like you'd prefer it to exit and keep running in the background, in which case you should use pg_ctl to start the server instead.
The bigger problem is that those instructions are pretty stupid. You shouldn't be initdb'ing a new cluster and starting a new server; you almost certainly have one installed and running. It's hard to say, since you didn't say how you installed PostgreSQL, what OS you're on, what PostgreSQL version you have, etc.
In general, though, you should be connecting to your existing PostgreSQL install. Use that, don't initdb a new one. That's why the guide you were reading says:
This section may be unnecessary on your system. Check if your installation of postgres created a default database and start scripts for you.
Since you're using a stock Ubuntu install, please start by reading the Ubuntu introduction to PostgreSQL.
Then follow the setup guide starting at "create the database".
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
our existing Database size around 200Gb,if we can use consistent,parallel backups methods.
for testing i migrated development Db from 5.5 to 5.6 by taking mysqldump with option --single-transaction,but for production i am looking for way where i can upgrade mysql prod Db to 5.6 with minimal downtime.
You can build a new server and install 5.6 in that machine and migrate data while keeping your existing DB up and running.
Once you are ready you can just flip the connection string in your app or change the IP address. This will give you no downtime but will require to setup another machine. It's usually easier when you are using cloud hosting (AWS, Rackspace etc).
Another alternative is you might as well put up a expected downtime page in advance if it's not a mission critical application.
You cannot upgrade 5.5 to 5.6 so the best way is to start a new 5.6 server machine dump the database from 5.5 and point your app to the new server. For huge data migration you can take a look at jetpants to migrate massive data.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I'm maintaining a simple web site written in Perl in my copious free time, and I don't want do my coding on the live website any more, instead checking if the changes work on a local machine first.
As far as I can tell, the web site runs on apache.
Should I install apache on my local machine, or are there simpler (but well documented!) options more suited to a development box?
Related question: How can I run Perl on web servers? , but seems to be talking about a production box, not a development box.
XAMPP is an excellent package for precisely this purpose. It includes Apache, MySQL, PHP, Perl, and other tools, all pre-configured to run on your local machine. I use it for WordPress, but I expect that it would be equally good for Perl CGI development.
I use it on Windows. It is also available for Linux and Mac.
Hat tip to Kenosis, who mentioned XAMPP first. I didn't see that at the time.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Trying to install PGSQL on Windows Server 2008 SP2 (not R2) x86_32.
Got errors like "Problem running post-install step. Installation may not complete correctly. Failed to start the database server" and something like that.
And also installation doesn't fill data directory - it empty.
I tried start PGSQL manually via pg_ctl(register and start) and initdb, but nothing works.
Reinstalled many times with removing postgres user via Computer Management and his folder. Again, no result.
Guys, maybe you have good manuals or experience about deploying PGSQL on Server 2008?
Anyone else running issues should read Common installation errors, Troubleshooting Installation and the Guide to reporting problems.
This known issue with some Windows systems is documented there, and advice on how to report issues with enough info to get an answer (including installer logs, etc) is also provided.
I've got solution.
http://forums.enterprisedb.com/posts/list/2448.page
Just register vbscript.dll and associate VBS files with scripting engine.