I just installed Liferay standalone on my local development laptop and started it.
PROBLEM: The log prints this every minute:
07:01:36,157 INFO [Thread-33][LCSClusterEntryTokenAdvisor:238] Unable to find the LCS cluster entry token file
07:01:36,167 INFO [Thread-33][LCSConnectorRunnable:73] Unable to get LCS cluster entry token
07:01:36,167 INFO [Thread-33][LCSConnectorRunnable:111] LCS portlet is not connected
07:01:36,167 INFO [Thread-33][LCSConnectorRunnable:127] Retry in 60 seconds
It is very annoying. How to fix the root problem, or otherwise prevent this from getting printed?
My exact version is 7.0.10 GA1 (EE DXP 7.0 SP3 fix pack 15-7010).
The only "configuration" I did was to tell the wizard to use MySQL.
If you are on non-production environment go to bundles\osgi\marketplace and just delete the Liferay Connected Services Client.lpkg. Hope this helps.
There was an issue with lcs connections that seems to have been fixed by now.
If the message is still appearing, you could also check if there is an updated version of the lcs portlet available or just change the log settings as a last resort. Or, as it's the enterprise version, just open a support ticket.
Related
After upgrading system to Windows 10 - os 1803 we are getting below issues while working with ClearCase 8.0.1.x/9.0.1.x
Unable to checkin/checkout.
Not able to create views.
Not able to add any file to source control.
The system hangs & crashes while performing any ClearCase operation.
There is no error message, but I have attached screenshot for reference.
Please let us know if there is any issue with the Windows 10 ver(1803), any security system enabled?
Or has ClearCase provided any fix?
We have tried 9.0.1.5 and issue still persists.
This is what we got from windows event log.
The computer has rebooted from a bugcheck.
The bugcheck was:
0x000000c2 (0x0000000000000004, 0x00000000535be990, 0x000000000004efd3, 0xfffff803e01848b1)
for most of them whoever has upgraded to windows 1803 ver :( for people who are still using ver1709 it is working perfectly fine
Then I would recommand contacting IBM support: only them can update their ClearCase 9/Windows 10 compatibility matrix and confirm if MVFS is supported on a more recent (1803) Windows 10 edition.
We also facing same problem and I have raised the case with IBM. Still not yet resolved. As IBM said there are some limitations to work ClearCase with windows 10 and windows 2016.
We tried all the options except Secure boot disable. If possible please do disable secure boot option in Windows 10 and try to checkin/checkout code from CleraCase
Note : It works for Snapshot views. That means the issue related to MVFS
I'm seconding #VonC's recommendation to open a ticket with IBM. When you do that, save a step and collect a clearbug2 and a kernel memory dump to send in as soon as the case is opened. It will save the turn-around time of us asking you for it. If the installed programs list doesn't list installed security software (DLP, Privilege management sw like Avecto, other endpoint security tools), please list those separately as well.
I would also love to know who # IBM told you there are "limitations" with Win10-1803.
There are a few issues with Windows 10 "version upgrades" breaking things, but they generally don't cause system crashes. Windows 10 upgrades are actually full OS installs that then (imperfectly) migrate application settings. Anything that uses custom network providers (ClearCase is one example) will find that the network providers will be broken or partially broken. Reinstalling is usually required. Again, that has not yet been reported as a cause of a BSOD.
If the upgrade/reinstall didn't fix view creation, please post a separate question on the view creation issue. There may be things we can do to the SMB 2 caches to allow view creation to work in cases where the view storage is not on the client host.
I noticed that the screen shot you posted is a Terminal Services disconnect screenshot. Does the issue only occur over a Terminal Services client connection or does it also happen on a local connection?
I have API Connect installed with mongodb connector over a remote server.
When I access the IBM API Connect through browser, all is fine, but when I go to DataSources where my DB is, and try to hit Update Schema button as shown in the image, an error occurs showing this:
Cannot GET /apim/dataSources/partials/dataSourceMigrate.html
P.S. I gave full permission for my project directory (/var/www/) with full ownership for www-data group and still the same.
Anyhelp would be appreciated.
FINALLY AND AFTER 2 MONTHS OF WAITING, I've got an answer from IBM Bluemix Support and sorry to bring the bad news, which is the following:
Hi Ghassan,
Thanks for sending the additional files. I checked with our development team and they found a bug in the code.
The fix will be available in a future release of the apic command line, but I don't have a date for it yet.
I will further discuss the plans to release this fix and will update you as soon as possible.
IBM Bluemix Developer Support and Enablement Team
A fix has been provided for this issue in iFix versions of 5.0.3.0, 5.0.4.0 as well as newer versions of API Connect. If you are still experiencing this issue, please update to a later version that includes the fix.
I'm having a strange issue with my (i admit) very old liferay. Sometime yesterday morning my system broke down and doesn't start up again. I have no idea why it broke down.
Now when I restart my liferay again according to the logfile it starts fine. But when I try to acces the page via browser all I get is inifite loading. No log messages, no exceptions, no timeout, nothing. This all was Liferay 6.0.5 and JBoss 5.
I then downloaded a Liferay 6.0.6 bundle with Tomcat 6 and connected it to my oracle db. Same behavior. Next thing I did was not using an oracle connection so liferay used its built-in memory DB. And voila, startup worked immediatly. reconnecting to oracle results in failure again. I tried this liferay-tomcat bundle with all needed themes and portlets.
Then I undeployed all custom webapps and startet again and suddenly my log showed this message: No theme found for specified theme id <MY_CUSTOM_THEME>. Returning the default theme.
So the request must reach liferay somehow. Sadly the browser still doesn't show anything.
I'm short on ideas so I'm grateful for any help. Btw: I'm planning to relaunch with liferay 6.2 and an other db schema in couple of weeks, so a dirty workaround would totaly be enough for me.
Thinking out of the box: Is it possible to export all data from my database as sql inserts, etc and import them into liferays memory db? I know the memory db is not build for production use, but since it's only a couple of weeks I might give it a shot.
EDIT: I switched back to my jboss 5 and liferay 6.0 setting. I just noticed another strange thing. When I type a non-existent like liferays default community url (not configured in my particular portal instance) I see this message in my log Current URL /de/web/guest/home generates exception: null
. So apparently the illigal requests are recognized but legal requests are not served.
Thanks guys and regards. Sebastian
I am facing issue while doing the publishing site/publishing content in sitecore. The publishing window always stuck at initializing.
Sitecore Version: Sitecore 6.4 (rev. 110720)
Log Error i am getting:
WARN Long running operation: renderContentEditor pipeline[id={FBD9E5F6-D571-487F-BA27-2B95E9F51022}]
This id in the log is the current item ID on which i am doing the publishing.
For all item in sitecore i getting this same issue.
I already restart the IIS and recycle the App-pool.
Please suggest me any answer for this issue.
Regards,
Deepak Narwal
Take a look at the following three database tables in the Master database. If they have more than a few hundred entries, clear the tables:
History
EventQueue
PublishQueue
After you do that, recycle the authoring instance's app pool and try again.
A while back I have collected together links to a few blog posts, as well as my own investigation, of some of the reasons you might have this issue:
https://theagilecoder.wordpress.com/2013/09/30/sitecore-publishing-stuck-on-initializing-after-applying-scalability-settings/
Similar questions are on SO here that may help you investigate:
Sitecore Site/Item Publishing hangs at Initializing
sitecore publishing initializing
we followed the article at http://support.microsoft.com/kb/927675/en-us to implement the pdf filter for wss 3.0.
But the registry entry mentioned on step 2 (adding a new entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Applications\GUID\Gather\Search\Extensions\ExtensionList) is lost if we reboot the system.
Does anyone have any idea why that might be happening?
We installed the adobe reader 10 and tried to configure the pdf filter for wss 3.0
Ok, found the problem. After changing the registry you have to stop and restart the share point search service. No idea how they are related tho!
Following are the commands:
net stop spsearch
net start spsearch