I'm having trouble starting a Couchbase 2.5.1 enterprise edition server process with Memcached buckets. I get a permanent "server down" message when I navigate to:
http://localhost:8091/index.html
The server logs just give this error for all the buckets I create.
[error_logger:error,2014-09-02T11:45:58.320,ns_1#127.0.0.1:error_logger<0.6.0>:ale_error_logger_handler:log_msg:119]** Generic server <0.2989.5> terminating
** Last message in was {'$gen_cast',
{connect_done,4,
{error,couldnt_connect_to_memcached}}}
** When Server state == {state,4,0,0,
{[{{stats,<<>>},
{<0.2341.0>,#Ref<0.0.8.143607>},
{1409,638548,233000},
2}],
[]},
{[],[]},
{[],[]},
connecting,undefined,"Customer",
still_connecting,undefined,[]}
** Reason for termination ==
** {bad_return_value,{stop,{error,couldnt_connect_to_memcached}}}
I'm running Windows 8.1 x64 and Couchbase 2.5.1. What's odd is that on another machine with the same setup, I can run Couchbase just fine. After searching on the Internet for a while, I found this link: http://irwinj.blogspot.in/2013/03/installing-couchbase-on-windows-8.html, but that's for Win8 + Couchbase 2. The referenced bug link says the issue has been fixed. So, I'm not sure what to do next next.
Any pointers would be great.
Thanks!
ps: If this question belongs to a different stack-exchange website, please let me know, I'll migrate the question there.
Related
I experienced the following error after installing Information Server Console 8.1 on my windows xp sp2 workstation when I try to log on Information Server Console:
"Internal Error: - Failed to load the Java Virtual Machine. The most common cause of this error is a failure of Java virtual machine to allocate enough memory" Check the memory settings in ......\proxy xml.
I attached proxy.xml for your documentation. Besides my workstation has 4 Gb RAM and Sun Java Runtime Environment v 6.0_11.
"Other possible reasons for this failure are that one or more JARS are not present or some other configuration problem exists." Not very disclosing I suppose ...
I set the environment variables : XMOG_TRACE_LEVEL= Verbose and XMOG_TRACE_FILE=c:\xmogtrace.txt, tried to log on again, but no file or information is generated on c:\xmogtrace.txt and the error is the same.
Please see the following technote in ibm.com which discusses solution for this issue:
http://www-01.ibm.com/support/docview.wss?rs=14&uid=swg21370513
Our application has been changed from ".exe" to virtual application launched via "Microsoft Application Virtualization Client".
QTP is unable to identify any objects even with the same add-ins (which was working before). What could be the possible reason for the odd behaviour?
QTP : 10, Win7 64 bit OS.
Let me know for additional info. Thanks in advance!
When this application is launched via Microsoft Virtual Client it has limited interaction with local applications. For the same reason QTP\UFT is unable to identify the object of AUT. To overcome this issue you have to set "LOCAL_INTERACTION_ALLOW" to TRUE in the Application OSD file.
You can find the file in the OSD Cache folder in the program data of Microsoft Virtual Client.
We record our office IP phone activity using Xima software's Chronicall, which uses a PostgreSQL backend. The server on which both of these are installed is an ESXi 5.5 VM running Windows Server Standard 2008 SP1. For some time now, we have been getting the following PostgreSQL errors in Windows event viewer:
"FATAL: could not reattach to shared memory (key=248,
addr=02510000): 487"
"WARNING: worker took too long to start; cancelled"
These errors occur every hour or two, and always occur back-to-back in the order listed above.
Xima support has looked at the issue multiple times and has not been able to resolve it. Upon their recommendation, I have upgraded Java, disabled antivirus, and run the Windows Memory Diagnostic Tool (came back clean), but the errors persist. Xima has specifically stated that PostgreSQL should not be updated, as versions above 8.3.7 are known to cause other issues with Chronicall.
Any other suggestions to resolve this issue?
I would say the company (Xima) is at fault here, since PostgreSQL 8.3.7 is hopelessly outdated.
Quoting the official Versioning policy of Postgres:
Postgres 8.3 has reached EOL in Februar 2013
Moreover, Postgres strongly recommends:
We always recommend that all users run the latest available minor
release for whatever major version is in use.
The latest point release of 8.3 is 8.3.23.
Version 8.3.7 is just not right.
Running Postgres on a Windows Server 2008 VM wouldn't be my first idea either...
I've successfully configured ZSS Server on my internal system (Win Server 2008R2 + IIS 7.5), and everything works fine.
Now I'm trying to install the same system on a customer machine; I've done this through the installer (latest version), he has applied the necessary security permissions, the home page of the site is visible, but syncing the db give the 1992 error.
Taking a look at IIS logs, I see that every call with GET /pull result in a 404 error code, subcode 0; there are several consecutive statements like this, all terminating wi9th 404.0 error code.
The web.config is the same as my system. What else can I check ?
You say you can reach the home page of the site - do you mean the "main" IIS home page, or the root of the ZSS site? That is, assuming Zumero is running on port 8080, what do you see when you point a browser at http://your.customer.site:8080?
I my case it was caused by the Application pool being configured for 32 bit (which it should not be). Version 1.4 has an improved installer, that should prevent this from happening
We have an application server with the following spec’s:
• Windows 2008 R2 operating system.
• All prerequisites are configures successfully and correctly: Windows roles, MSDTC and connection to SQL DB server.
• MS Reporting Services 2008 R2 are installed and configured successfully, and all reports are deployed and render with no problems.
The application server connects to SQL Server 2008 R2 DB on different server - there are no firewalls between the 2 servers , and using UDL file, the connection is always successful using windows authentication or SQL authentication on SQL Server.
When we install “K2 blackpearl 4.5 (4.10060.1.0) with Update KB001040”, the setup completes successfully but the following exception appears when we open work list, when K2 setup manager is opened for reconfiguration and when rendering any report on the report manager: “A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)” although all DB’s are created successfully during the installation for K2. Also all other features at K2 (any feature at Management Console) and Report Manager (deployment of reports, management of data sources, and folder/report settings) works perfectly.
When we remove K2 components from the server the reporting services works successfully again, without any reconfiguration.
We tried to move the server to new environment to check if there is a problem with the server itself, all installation and configuration are completed with no problems and the error message disappeared.
We did check all of below points:
• MSDTC configuration.
• All ports are open between the 2 servers.
• SQL connection is always successful between the 2 servers.
• We have a third server with MOSS 2007 installed and it works perfectly with problems in connection to DB.
• All users used for windows services and SQL windows connection are active and configured correctly.
o Have SQL login with dbcreator and SecurityAdmin roles.
o Are added as Administrators on Application server.
• We have tries Windows authentication and SQL authentication and they all gave the same problem.
• We have used a newer version of K2 installation files “K2 blackpearl 4.5 (4.10060.1.0) with KB001320” and it failed at the last steps of installation with the same problem.
Please help on this.
(full disclosure i work for K2) and looked through our system as well as the support forum and could not find a reference to this error. From the people i talked to it appears to be a general network issue, with quite a few possible causes, including something as simple as the network card. Although I am not 100% clear on a few points you made. When you said
"following exception appears when we open work list" Where are you opening the worklist from?
When you said
"When we remove K2 components from the server the reporting services works successfully again, without any reconfiguration."
Are you getting this error in SQL Reporting Services?
You can also post a question in http://k2underground.com someone else may have seen this.
Edit I asked around and there does not seem to be any good answers to this at the moment. Would you be willing to open a K2 support ticket and let us look at the K2 logs or see the config via livemeeting? Thanks!