I'm running GitLab on Centos 7. GitLab was installed using YUM.
The initial gitlab version was 1.7.12.2.
The problem is with the WEB interface of the GitLab installation.
I'm trying to get the browser session to timeout so that it forces you to login again after a certain period.
I have noticed that a change request was implemented, so I upgraded from 1.7.12.2 to 1.7.14.3 using yum update.
Under the Administration setting (in Web UI) I can now see the extra parameter where you can set the timeout. I have now changed it tt two minutes(for testing so I don't have to wait so long), but it simply does not work.
I have also tried something bigger - 5 minutes - not working.
I have also done a gitlab-ctl stop, then gitlab-ctl reconfigure and then gitlab-ctl start. The new value still shows, but the browser session still does not timeout.
I have also created a new CentOS 7 installation from scratch, installed GitLab via yum with version 1.7.14.3 - this is as-is from the installation - so no previous upgrade problems or similar problems.
I have tried different browsers (FireFox and Chrome) on Windows 7/8, Even Mac. I have also cleared the browser cookies to make sure it gets the latest after the updates. No change in behavior.
Changing the time still has no effect....
Anybody with an idea what I'm doing wrong?
The truth is I think there is a bug in the current session expiration mechanism. See https://gitlab.com/gitlab-org/gitlab-ce/issues/2129
Short answer, your not crazy ;) Hopefully we can resolve this issue shortly.
Related
I hope this is the right place to ask. I was thinking serverfault might not be correct, since the computer in question is not a server. Feel free to migrate if StackOverflow is not right.
I usually install IIS on servers but have installed it on Workstations before. I actually had the same problem with another machine of the same model a few weeks ago but can't remember how I resolved it. I must have installed additional features or run some powershell-command that did not resolve the issue on this machine.
I installed IIS the correct way using the Windows Features, as described in the answers to this question. I've actually removed and reinstalled it since then, but it hasn't resolved my problem.
The WWW publishing service is running and I can open the IIS Manager, but it's completely empty, unlike here where the IIS Manager at least shows the local computer
When I type localhost into a browser I don't see the IIS Startpage, I get the error ERR_CONNECTION_REFUSED
You can see that all the required checkboxes are checked:
And the service seems to be running.
I've since tried installing IIS using
DISM:
Powershell:
And I checked the status using the iisreset command which was mentioned in the comments here (second linked question upstairs):
It restarts without any error and says everything is working fine.
Has anyone ever encountered this before or might know what I could try to get IIS actually working?
Edit:
I just noticed, while trying to uninstall IIS, that I can not uninstall it. I used Windows-Features and confirmed to reboot when prompted, but while rebooting Windows does a rollback and IIS is still available. So I can't even uninstall it.
Also just found this similar quesion on SuperUser. I'm still trying some suggestions there. So far to no avail.
Thanks for the comments.
I was on vacation, but a colleague was able to fix the problem.
Unfortunately, the solution was to reset Windows 11. He was then able to install IIS through Windows Features and it worked.
No idea why it didn't work in the first place, or why it got to this unrecoverable state. But now everything is fine.
I try to start a new Typo3 project with v11 on my local system (Windows 10, XAMPP for Windows 7.4.13, PHP 7.4.13).
The project was created with composer as suggested, using 'composer create-project typo3/cms-base-distribution'.
During the typo3 install process I got no php configuration errors.
In the php.ini I have set max_execution_time to 240, max_input_vars to 1500 and memory_limit to 512M.
After installation however I neither can access frontend nor backend.
I just receive a timeout message in firefox.
Admin Tool is working, though. I get no errors analyzing the database structure.
Has anyone an idea what I am missing?
I can confirm that the installation with composer in Windows has still problems.
In my case the database-table be_sessions wasn't created and the installtool wasn't working.
I also used xampp, but an older version than you did use.
I never had any indication that the problems are related to composer so I think that they are still related to TYPO3 itself. The current version 11.0.0 is not considered as stable yet, so usage is experimental or for further development but not advised for production.
Before I installed with ddev and I never remarked any fundamental problems.
I could open frontend, backend and created a content-element without any problems.
Even I use ddev in Windows the operating system is linux, so probably your problems are related to some Windows related issues.
The installation-guide for TYPO3 can be found here.
There never keeps more to say than using either the currently stable version 10 or another operating system.
I build my project on Travis CI. I run tests the following way:
Run Firefox with index.html parameter, which loads script that attempts to connect repeatedly to websocket server.
Run simple websocket server that sends commands to Firefox.
Script in Firefox reads these commands (they may contain some JavaScript code to test), executes JavaScript code.
This works when I run things locally. This also used to work on Travis a couple of weeks ago. However, things that worked for years, had broken unexpectedly. Firefox reports no errors, but node.js server receives no incoming connections for some timeout. I don't know the way to debug the problem. Script that runs in Firefox uses console.log extensively, however I can't retrieve these logs from Travis. Is there any way to get some information from Firefox that runs on CI server?
Note: I run Firefox 53. After things got broken, I tried to upgrade to recent version. Also, I used to run following commands before running Firefox:
export DISPLAY=:99.0
sh -e /etc/init.d/xvfb start
sleep 10
And I tried to remove these lines and use headless more, however this didn't work.
Script that runs in Firefox uses console.log extensively, however I can't retrieve these logs from Travis. Is there any way to get some information from Firefox that runs on CI server?
Firefox 65+ supports a new devtools.console.stdout.content about:config preference, which you can set to true to make the Console output be dumped to stdout (and appear in Travis, I believe).
There doesn't seem to be a good solution for earlier versions: Selenium's driver.get_log() doesn't work in Firefox, and other solutions look unsatisfactory to me.
You seem to run index.html as a file:/// URL, in my opinion that's asking for trouble - I recommend spending time to set up a local https:// server, to save time debugging ever-increasing "security" restrictions the browsers add for non-https content.
If the above doesn't help, try reproducing this with a minimal testcase in a separate repo; if the problem persists, you can share that repo in another question.
You can run vnc with xvfb and connect to it with vncviewer. Here you have some more details: https://www.alexkras.com/debugging-xvfb-server-with-vnc/
I must have done over 100 installs of DNN (dnnsoftware.com) now, and I have never seen the "wizard" complete correctly. It always hangs at 28%. Upgrades usually hang at the 53% level.
This appears to be a user interface fault, because if I wait long enough - how long? - I can navigate to the site and all is working perfectly. If I don't wait long enough, some part of the installation process restarts and gives me a site without a superuser account.
The installation process does not appear to have been adequately tested. Anyone know how to get the "wizard" to complete correctly?
I haven't experienced this high of failure rate with the installation or upgrade.
In order to diagnose the problem, do an upgrade. Before applying the upgrade, set the AutoUpgrade key in the web.config to "false". Then initiate the upgrade by going to:
[baseurl]/install/install.aspx?mode=upgrade.
Instead of the simple progress bar, you will get a detailed report of the extensions and items being installed or upgraded.
Before installing, make sure your file permissions are set appropriately on the website folder and you follow all of the steps as per the installation guidelines.
Also, if it turns out the issue is timeouts during the install due to a slow server, try increasing the execution timeout in the web.config in the <httpRuntime> node. The default executionTimeout is "1200" which is 20 minutes. if your upgrade or installation is taking longer, increase the value.
I keep getting the error:
FATAL: sorry, too many clients
already
I never had the problem before, but I recently upgraded to version 9.03 and also OS X lion preview release 2. It doesn't seem to matter how idle the processes are, they never die. I have to restart postgres every half hour or so. I'm using postgres via Rails 3 and Navicat, never had a problem with either before now and stopping both clients does nothing to solve the problem.
Any ideas or settings I'm missing? Not sure what settings I should display here for my setup, but everything should be default. Installed postgres using HOMEBREW.
Most likely go into postgresql.conf and edit max_connections and post the existing value.To see how many connections you have an what they are doing select from pg_stat_activity. Maybe your bleeding connections?
See this link
http://www.postgresql.org/docs/9.0/interactive/runtime-config-connection.html