On my system, there are users about 20,000+ , but I can not finish to import users from openLDAP. The Users was imported until 10,335 and they just stop to import. It's seem they just stop at 10,000 without any log error.
(Before, I just could import user about 1,000, but I search another sites and someone suggest to use ldap.page.size , so I try to use ldap.page.size=30000 and they just stop import at 10,000)
My Server:
- liferay-portal-tomcat-6.1.2-ce-ga3 (bundle with tomcat)
- PostgresSQL9.3
- Open LDAP 2.4.23
My config:
ldap.import.method=user
ldap.page.size=30000
index.search.limit=50000
organizations.search.with.index=false
users.search.with.index=false
I have restarted many times but no more any user import to Liferay.
Help me please!!
This is not affected from Liferay end and also page size is for number of records fetched in one go by LDAP,hence the above solutions do not work out well.I do not have openLDAP server installed currently but as per the given link openLDAP specs, these limits are specified from ldap end in order to maintain system performace.Try fiddling with cachesize and idlcachesize properties(both with default values of 10000),at openldap side,to fix this limitation.
Let me know your findings.
Related
I'm running a Dash/Flask app on Windows Server 2019 with IIS. I installed IIS with CGI, installed wfastcgi in the app's virtual environment, ran wfastcgi-enable as an administrator and specified the FastCGI application as a route handler in web.config using the virtual environment's python executable and wfastcgi.py file, etc.
That all went smoothly and the app is up and running. The app redirects to '/' to login if the user is logged out. This all works perfectly when I run the app on Flask's built-in server, but only works periodically (i.e. sometimes the user is no longer logged in, after the redirect, or refreshing the page logs out the user by chance) in this IIS/fastcgi setup. I use flask-login to login and authenticate users, following closely the example given here: https://github.com/RafaelMiquelino/dash-flask-login.
I also tried to configure flask-login's remember me functionality to persist the login after browser close, but this didn't change the mentioned issues.
Has anyone else experienced this? I'm open to any ideas on why I'm experiencing this strange (session?) behavior with IIS and FastCGI.
Thanks!
EDIT:
Moreover, I did some more tests and found that it is not only random logouts, but also some kind of "random logins":
1. User logs in at login page and is redirected to the "real" content located under /success: Message: User could not be authenticated.
2. Reloading the webpage "/success" without any further action: User is authenticated and can see the content. After repeated reloading the same user is randomly authenticated or not.
Try to increase the iis application pool recycling and ideal time out value.
increase fast cgi ideal time out:
Make sure you set app.secret_key to some secret key. yo could get key by following below code:
import os
os.urandom(24)
Use the following command to quickly generate a value for Flask.secret_key (or SECRET_KEY):
$ python -c 'import os; print(os.urandom(16))'
b'_5#y2L"F4Q8z\n\xec]/'
Refer this link for more detail:
flask-login invalidates session randomly after authentication
https://flask-login.readthedocs.io/en/latest/
I have ran a SQL script to update the UserPreferences.UseLegacyUI to 0 for all of the users in our 2018 R1 system but, the users are still getting the classic UI when they log into the system. Any thoughts on why this might be? We're trying to avoid every user having to change their setting in their profile.
EDIT: Users are having to switch to the modern UI every time they log in. Is there a cookie involved?
Try using the UserPreference graph to change that value, that's how it's used in 'Main.aspx.cs'. Sometimes there's code in event handlers that needs to be executed too:
PX.SM.SMAccessPersonalMaint prefGraph = PX.Data.PXGraph.CreateInstance<PX.SM.SMAccessPersonalMaint>();
PX.SM.UserPreferences prefs = prefGraph.UserPrefs.SelectSingle() ?? prefGraph.UserPrefs.Insert();
prefs.UseLegacyUI = false;
prefGraph.UserPrefs.Update(prefs);
prefGraph.Persist();
There was an HTTP redirect set in IIS on both the web site and the web application that was causing this. I suspect this was a hold over from the 5.3 installation but, not sure. Removing the redirect from the web application and removing the "/main.aspx" from the web site redirect cured this issue.
I have installed Drupal 7 on a sub domain caihr.sieaegroup.com. I closed the browser and now am unable to log in to any of the admin pages. I get no login form and I am not using the default theme.
I have cleared cookies, tried different browsers but nothing works. Am I missing something? Do I need to update the .htaccess file?
This is the second time I have been down this road. The first was to reinstall drupal and start from scratch without logging out or closing the browser but I feel this is not the right solution.
Any Help is welcomed.
If you logged out and default theme can't provide proper login form you have to change to some functional theme and then login:
https://www.drupal.org/node/200774
It says:
activate a trusted theme
UPDATE system SET status=1 WHERE name = 'garland';
change the default setting
UPDATE variable SET value='s:7:"garland"' WHERE name = 'theme_default';
clear the cache tables
TRUNCATE cache;
TRUNCATE cache_bootstrap;
TRUNCATE cache_block;
Use phpMyAdmin or some similar tool to execute queries.
temp:=#DbLookup("Notes":"NoCache";"ARRoW/SSS":"sss/sssProj.nsf";"(Lookup for Community)";"State of Maine";2);
temp1:=#DbLookup("Notes":"NoCache";"ARRoW/SSS":"sss/sssProj.nsf";"(Lookup for Community)";"State of Maine";3);
temp2:=#DbLookup("Notes":"NoCache";"ARRoW/SSS":"sss/sssProj.nsf";"(Lookup for Community POC)";"State of Maine";4);
#If(#IsError(temp)|#IsError(temp1)|#IsError(temp2);"Error";temp + " " + temp1 + " " + temp2)
Hi this works on Lotus Notes Client but doesn't work on web Any help is welcome thanks in advance!
There are typically three types of root causes for something like this.
One type of problem is server trust. This only applies if there are two servers involved. I.e., the web server is ServerX/SSS and the code is trying to access ARRoW/SSS. You need to review ARRoW/SSS's server document and check whether "ServerX/SSS" is listed in the field for "Trusted servers". (Also note that if this is a really, really old version of Domino - before version 6 if I recall correctly - then the trusted servers feature is not there and you cannot make cross-server calls to #DbLookup in web code.)
The second type of problem is that the server where the code is running can not resolve the name of the server where the database lives. The code is accessing server ARRoW/SSS, but you haven't said whether ARRoW/SSS is the actual web server, so let's look at both cases.
Assuming that it is all happening on one server, there can still be a name resolution problem because of the way the formula is coded. Try specifying "":"sss/sssProj.nsf" instead of "ARRoW/SSS":"sss/sssProj.nsf". If that fixes your problem, great! But it means that you still have a problem either in your server document or with the DNS configuration on your Domino server and you should address that. You should probably continue with the troubleshooting that I give in the next paragraph. Just bear in mind that everything I say there is true even if ServerX/SSS is really the same as Arrow/SSS.
If the code is running on web server ServerX/SSS, then you need to make sure that ServerX can connect to ARRoW/SSS. The easiest way to do this is to bring up the console for ServerX and enter the command 'trace ARRoW/SSS'. If it fails, check the server documents and/or connection documents for correct IP addresses or host names, and open a command window on the server and try a ping using the exact information in the server documents. If it fails, you have a networking issue. One of the underlying causes I've seen for a problem like this is that there is no connection document (because the servers are in the same named network, but neither the IP address nor the fully-qualified host name is entered in the networks table in the server document, so Domino just asks DNS to resolve the common name 'ARRow' - but the DNS configuration on the web server does not include a default search path so the name is not resolved. But you need to check everything until you can get a 'trace' command to succeed.
The third type of problem is Access Control. This is a broad category that comes down to the fact that the identity that the code is running under either does not have access to the server ARRoW/SSS, the database sss/sssProj.nsf, the view (Lookup for Community)" or the document(s) with the key "State of Maine". There are a lot of things to check. If the code is running in a field formula, the identity is that of the user, and if the same user does not get the error through the web client then you need to look at the database properties for sss/sssProj.nsf and check the maximum web access level. If the code is running as an agent, you need to check the agent properties to determine what identity the agent is running under, and then review everything: the security settings in the server document, the database ACL, restrictions on the view, and reader names fields in the documents.
I have set up solr and it works. I have tested it by indexing my MySQL db and running queries on it, trying facets and trying the term suggest component (which I wish to use with autocomplete).
I have recently walked through the reuters tutorial here and it worked on my local machine.
Now my solr instance is on: "http://[someurl]::8983/solr/" and the instance they are using in the 'reuters.js' file is 'http://example.solrstuff.org/solrjs/'. How do I change the code to point to my instance - when I just swap the urls the code in the example doesnt work anymore - no search results are displayed. Do I need to install SolrJS or something? What is going on here?
Any help appreciated!
Do you have a typo in your URL? It looks like there are two colons in between the domain and the port number. http://[someurl]::8983/solr/ should be http://[someurl]:8983/solr/. You can test by entering that URL into a browser on your test machine. You should be able to get to the Solr admin page from there and do a query. If you can't, it's a problem with your URL.