Jump to content

CreZo

Members
  • Posts

    24
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

CreZo's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Good morning guys, I solved the problem. I found this topic and my problem was pretty similar after I checked the log files. I bought a new flash drive and since then everything works fine now. Thank you so much!!!
  2. Thank you, Frank and trurl for your answers. I already did this Frank and there was no reboot or anything else. I also stopped all VM's and apps. Every time I got the same result, a popup with the message in it but the server didn't reboot or shut down. The server is still running. I don't get it but I will the 'Troubleshooting mode' and also the Temperature problem can be a fact maybe this can help.
  3. Hey Frank, old hardware: Motherboard Gigabyte Technology Co. Ltd. Z170-HD3P-CF (U3E1) CPU Intel Core i7 6700K new hardware: Motherboard Gigabyte GA-B250M-DS3H CPU Intel Pentium G4560 (2x 3,5GHz + HT) Yes, it does. Yes, no errors. I don't know which hardware is failing. I boot the server and everything is fine for ~30 - 45 minutes. After this time when I login into the GUI I get a popup which tells me that there is an unclean shutdown detected. Also, the theme changed from dark to white. My docker and apps are still running but I can't see them in the dashboard anymore.
  4. Hey guys, I've got a huge Problem. I switch to another mainboard and CPU (power consumption is much lower) and I've got a popup which tells me that there is an unclean shutdown detected. This happens in ~ 30 - 45 min after I start/reboot the server. At the weekend I build everything in the old system and it worked perfectly but I want to use the new mainboard and CPU. Can someone help me?
  5. Thank you for your help! I add an extra file for the GitLab site in nginx, add the git.mydomain.bla domain in my DNS and now it works fine :).
  6. Hey there, here is my nginx conf: #GitLab location /gitlab { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.25:9080; } docker/ gitlab log after it's started/fully running: ==> /var/log/gitlab/nginx/gitlab_access.log <== 127.0.0.1 - - [19/Mar/2018:12:22:40 +0000] "GET /help HTTP/1.1" 200 28187 "" "curl/7.56.1" ==> /var/log/gitlab/gitlab-monitor/current <== 2018-03-19_12:22:44.75445 127.0.0.1 - - [19/Mar/2018:12:22:44 UTC] "GET /sidekiq HTTP/1.1" 200 11513 2018-03-19_12:22:44.75447 - -> /sidekiq 2018-03-19_12:22:46.65654 127.0.0.1 - - [19/Mar/2018:12:22:46 UTC] "GET /database HTTP/1.1" 200 54250 2018-03-19_12:22:46.65655 - -> /database ==> /var/log/gitlab/node-exporter/current <== 2018-03-19_12:22:48.13647 time="2018-03-19T12:22:48Z" level=error msg="ERROR: mdadm collector failed after 0.000131s: error parsing mdstatus: error parsing mdline: sbName=/boot/config/super.dat" source="collector.go:123" ==> /var/log/gitlab/gitlab-monitor/current <== 2018-03-19_12:22:48.93537 127.0.0.1 - - [19/Mar/2018:12:22:48 UTC] "GET /process HTTP/1.1" 200 3628 2018-03-19_12:22:48.93539 - -> /process ==> /var/log/gitlab/gitlab-rails/production.log <== Started GET "/-/metrics" for 127.0.0.1 at 2018-03-19 12:22:52 +0000 Processing by MetricsController#index as HTML Completed 200 OK in 0ms (Views: 0.1ms | ActiveRecord: 0.0ms) ==> /var/log/gitlab/gitlab-rails/production_json.log <== {"method":"GET","path":"/-/metrics","format":"html","controller":"MetricsController","action":"index","status":200,"duration":0.81,"view":0.13,"db":0.0,"time":"2018-03-19T12:22:52.852Z","params":[],"remote_ip":null,"user_id":null,"username":null} ==> /var/log/gitlab/redis/current <== 2018-03-19_12:22:54.09839 373:M 19 Mar 12:22:54.098 * 10 changes in 300 seconds. Saving... 2018-03-19_12:22:54.09851 373:M 19 Mar 12:22:54.098 * Background saving started by pid 6894 2018-03-19_12:22:54.10106 6894:C 19 Mar 12:22:54.101 * DB saved on disk 2018-03-19_12:22:54.10126 6894:C 19 Mar 12:22:54.101 * RDB: 2 MB of memory used by copy-on-write 2018-03-19_12:22:54.19871 373:M 19 Mar 12:22:54.198 * Background saving terminated with success extra params: --env GITLAB_OMNIBUS_CONFIG="external_url 'http://unraid:9080/'" I've got already a working domain https://mydomain.bla and I want to open gitlab over https://mydomain.bla/gitlab
  7. Hey guys, I'm going to plan a switch from Intel (6700K) to AMD ( Ryzen 7 1700X). What should I pay attention to or keep in mind?
  8. I've got the same Problem. Can someone help us please :D?
  9. Hey guys, I've got a problem with nginx and GitLab. I'm able to connect over http but https won't work.
  10. Thank you CHBMB for your help! I think the problem is my DNS provider. I can't point to the domain nextcloud.mydns.com (just an example). It only works with mydns.com/nextcloud. So can you recommend a good (maybe free) DNS provider? Edit: the problem (headers) in my old post are fixed, thanks! Now I'm only not able to install apps like the calendar for example :-/.
  11. I've got the same problem. Can you tell me how you fixed this problem? I read and followed the guide on Linuxserver.io but I can't find the problem for this error. Also, I can only open the nextcloud URL with the server.com/nextcloud instead of nextcloud.server.com. I used nextcloud on my old server with openmediavault and I'm new on unraid so I'm sorry for asking so many questions :D.
  12. I followed your guide CHBMB and the WebUI works for me but I've got still some errors like " Exception: The requested uri(/nextcloud/core/img/favicon.ico) cannot be processed by the script '/core/templates/404.php') at /config/www/nextcloud/lib/private/AppFramework/Http/Request.php#733 " and I also can't connect by the desktop client. It's telling me all the time that it can't find the status.php.
×
×
  • Create New...