MammothJerk
-
Posts
110 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by MammothJerk
-
-
My UPS is a bit finicky with the apcups plugin and does not always work correctly, NUT however always works and i created a small edit to the UPS section if you would like to add the option for NUT.
Firstly you need the "NUT Network UPS Tools" plugin for unraid and then the "maihai/nut-influxdb-exporter" docker to get the data to the influxdb database.
then all you need to do is change the variables around a bit and it works just the same as the apcups option
Attached is the UPS section of the main dashboard edited to work with NUT :).
-
I liked this dashboard so much i decided to install it on my other unraid box as well :), but i'm having an issue with CPU temp :(.
I cannot get my CPU temp from IPMI since this is an unraid box made from spare parts and lacks IPMI support, i can see the CPU temp in the unraid dashboard so i assume it should be possible to send that reading through telegraf, the question is how? the telegraf [[inputs.cpu]] seem to only take care of usage, not temperature.
the guide also seems to be missing [[inputs.net]] and [[inputs.docker]], i had to uncomment both of these to get any readings for network and docker on this other box.
Lastly just a minor thing, i run both my dashboards on the same grafana instance and i would like to be able to switch between them seamlessly in kiosk mode.
Currently i have "dashboard Links" setup on each dashboard to navigate to each-other, the problem is that this button gets hidden in kiosk mode, Is there any way to keep it on top even in kiosk mode? 😁
-
There we go 😁
It appears by default it is commented as "attributes = false" i had uncommented it which is probably what screwed me there, changing it to "true" has fixed my problem.
Thanks for your help
-
I fixed the diskio tags and i see where i was missing out on that one hehe.
It did not fix the POH issue though, removing the LIMIT didn't change anything either.
-
ah ok, it seems like there is no data so perhaps i screwed up with telegraf.conf? all i did was uncomment [[inputs.diskio]].
# Read metrics about disk IO by device [[inputs.diskio]] # By default, telegraf will gather stats for all devices including # disk partitions. # Setting devices will restrict the stats to the specified devices. #devices = ["sda", "sdb", "vd*"] # Uncomment the following line if you need disk serial numbers. #skip_serial_number = false # On systems which support it, device metadata can be added in the form of # tags. # Currently only Linux is supported via udev properties. You can view # available properties for a device by running: # 'udevadm info -q property -n /dev/sda' # Note: Most, but not all, udev properties can be accessed this way. Properties # that are currently inaccessible include DEVTYPE, DEVNAME, and DEVPATH. #device_tags = ["ID_FS_TYPE", "ID_FS_USAGE"] # Using the same metadata source as device_tags, you can also customize the # name of the device via templates. # The 'name_templates' parameter is a list of templates to try and apply to # the device. The template may contain variables in the form of '$PROPERTY' or # '${PROPERTY}'. The first template which does not contain any variables not # present for the device is used as the device name tag. # The typical use case is for LVM volumes, to get the VG/LV name instead of # the near-meaningless DM-0 name. #name_templates = ["$ID_FS_LABEL","$DM_VG_NAME/$DM_LV_NAME"]
ok i just re-read the front page and noticed i missed the part about the diskio tags 😬, ill fix that and test again
-
2 minutes ago, falconexe said:
Glad to hear it is working "awesome"!
Happy to help. Please post a screenshot of query on that panel. Should be easy to fix...
quick reply 😁
here ya go
{ "request": { "method": "GET", "url": "api/datasources/proxy/1/query", "params": { "db": "telegraf", "q": "SELECT last(\"raw_value\") AS \"Power On Hours\" FROM \"smart_attribute\" WHERE (\"name\" = 'Power_On_Hours') AND time >= now() - 12h GROUP BY \"device\" LIMIT 10", "epoch": "ms" }, "data": null, "precision": "ms" }, "response": { "results": [ { "statement_id": 0 } ], "executedQueryString": "SELECT last(\"raw_value\") AS \"Power On Hours\" FROM \"smart_attribute\" WHERE (\"name\" = 'Power_On_Hours') AND time >= now() - 12h GROUP BY \"device\" LIMIT 10" } } -
Thanks for your great work, this works awesome
The only issue i have is the "Drive Life" power_on_hours being the only graph not working, any idea what the problem is and/or how to troubleshoot it?
all my drives has the power_on_hours attribute but it's not being imported somehow
-
Recently i decided i wanted to setup tunnels on my 2 local unraid boxes to route all of their traffic through my VPN provider but for now it does not seem to be possible.
It seems like you can only use EITHER the remote tunneled access OR the VPN tunneled access, you cannot use them both at the same time so im either unable to access my local network from remote OR my local unraid boxes will not go through the VPN.
Is there a way to enable both "VPN tunneled access" AND "Remote tunneled access" at the same time? or a function that works similarly?
-
Currently i'm running the reverseproxy docker with duckDNS docker for updating my IP and it's working great.
I can access both dockers on my 2 local unraid boxes through a duckdns domain that gets authenticated through Organizr 2FA. With Wireguard VPN Manager i can access my network through the "Remote tunneled access" if i need to access any of the unraid webUI's for any reason or anything else on my network. it also works as a VPN for my remote location where it looks like i am connecting from my home address.
Now recently i decided i wanted to setup tunnels on my 2 local unraid boxes to route all of their traffic through my VPN provider but for now it does not seem to be possible.
Firstly it seems like you can only use EITHER the remote tunneled access OR the VPN tunneled access, you cannot use them both at the same time so im either unable to access my local network from remote OR my local unraid box will not go through the VPN.
Secondly it doesnt appear that i can use the reverseproxy when the "VPN tunneled access" is turned on because i would have to forward port 443 and 80 through my VPN provider which doesnt seem feasible.
So i sort of have 2 questions.
Is there a way to enable both "VPN tunneled access" AND "Remote tunneled access" at the same time? or a function that works similarly?
Is there a way to use reverseproxy if the host is connected to a VPN that cannot forward ports?
-
2
-
-
I'm also using Mullvad and running into the same issue as Monkeysphere and notcarl
I also had a question, is it possible to have "Remote tunneled access" and "VPN tunneled access" at the same time? i always want my unraid box to connect to the internet via my VPN but i also wanna be able to connect to my LAN remotely, and also take advantage of the VPN.
Is this possible?
the "Remark: this must be the only peer in the tunnel and sole active tunnel when in use" on VPN tunneled access seem to indicate this is currently not possible, but would it be feasible to implement?
-
On 8/13/2020 at 1:48 PM, binhex said:
rtorrent is well regarded as being able to support thousands of torrents, but even this does struggle when you get above 2000 torrents, so tbh you are probably best sticking with deluge if you are able to keep 6000 torrents active.
so one solution is to have two deluge instances and then split the load between the two, its not ideal i know as it means managing two deluge instances but it would work.
I figured out what the issue is
in libtorrent max_peerlist_size is set to 3000, increasing that solved my issue... for now... 😁-
1
-
-
14 hours ago, binhex said:
wow really!? 6000 torrents running deluge, i thought that was pretty much impossible!, there is no hard cap that im aware of but you will run into stability issues with that many torrents when running deluge.
This is the only real issue i've had so far. as long as i dont access any label that has 1000+ torrents in it it works as smooth as can be.
Is there another client i should be using if i have this many torrents?
2 hours ago, Wetterchen said:Did you have setup "Maximum Upload Slots" to -1 or 6000? You can find it under Bandwidth.
If you use "AutoAdd" so control the settings there too.i haven't changed these settings for a long time so i wouldnt think they are the cause..
-
Hey, i have an issue where whenever i restart my container i have a lot of torrents that have been paused, and i have to manually restart them, this has several issues where sometimes i will get an HnR warning and sometimes a torrent will just stop downloading completely.
I recently reached 6000 torrents in my client so i was wondering if there way maybe a cap there or something?
any help pointing me in the right direction would be nice, thanks.
Here are my settings
-
On 7/11/2020 at 8:18 PM, MammothJerk said:
My internet speed is 1000/1000 megabit and unraid is showing 100% CPU on transfers around 20-30 megabytes, if i cap the speed to around 10 megabytes my CPU is fine.
I'm using a btrfs cache pool, i was going to change it in the next unraid release but i should be fine with a bit lower space until then. I'll change it to xfs and see what happens.
I'm indeed using a Xeon CPU as well.
Tried installing unraid on an old pc running a 4770k and im DLing at around 30 megabytes/s and i'm not seeing any CPU spikes. Though since it's a completely different system and CPU is not the only thing being different im not sure how valuable this information is.
Good news, i split up my cache and changed the filesystem to xfs, now downloading for 15~minutes @ 50megabytes/second and my cpu is sitting at around 40% with periodical 100% spikes on any of the cores, which is pretty normal usage.
@SundarNET do you reckon the btrfs cache pool was your issue as well? perhaps your appdata folder is stored on the cache pool?
edit: i've actually noticed that all of my dockers are more responsive now, definitely seems to be an issue with btrfs cache pool...
-
1
-
-
On 7/9/2020 at 11:26 AM, binhex said:
im getting a little confused as to the speed that triggers the issue, is it 20-30+ Megabytes/s or is it 10+ Megabits/s, if its greater than 3 Megabytes/s then i will be unable to test this.
My internet speed is 1000/1000 megabit and unraid is showing 100% CPU on transfers around 20-30 megabytes, if i cap the speed to around 10 megabytes my CPU is fine.
I'm using a btrfs cache pool, i was going to change it in the next unraid release but i should be fine with a bit lower space until then. I'll change it to xfs and see what happens.
I'm indeed using a Xeon CPU as well.
Tried installing unraid on an old pc running a 4770k and im DLing at around 30 megabytes/s and i'm not seeing any CPU spikes. Though since it's a completely different system and CPU is not the only thing being different im not sure how valuable this information is.
-
6 hours ago, SundarNET said:
I must agree it was fine for a day but now yup 100% again and its directly correlative to the download speed anything over 10mbit peaks CPU use thank you MammothJerk for that one!
and I keep complaining because my system is a quad xeon server with 40 physical cores and 40 HT cores and when you see that shit maxx out its worrying
Only other thing i can find about this issue is people reporting a bad NIC, i've got an onboard intel-i210AT.
might have to invest in a new NIC if that is the issue.
-
On 6/29/2020 at 5:53 AM, SundarNET said:
I have been getting the same how old is your docker I had to remove mine and reconfigure it to stop this issue but just inmagine seeing that on 80 cores
Created a completely new docker, no plugins, with same settings and adding only 6 torrents, downloading at 20-30MB/s im still maxing out my CPU.
-
9 hours ago, bugster said:
Looks fine.
I'm guessing the host path you have is to a download folder under /mnt/user? Within Deluge > Preferences > Downloads. What paths are you using?
My downloads within deluge is set to "/mnt/user/Torrents" which would go through "Host Path 1" to "/mnt/user/Torrents" which in turn would actually be written to "/mnt/cache/Torrents" since the share "Torrents" is a cache-yes share.
-
4 hours ago, bugster said:
Can you post the container configuration to see?
sure thing
-
My CPU is hitting 100% after upgrading internet speeds.
I went from 100/100 to 1000/1000 the other week and now my unraid server is freezing up constantly with the CPU maxed out at 100%. I narrowed it down to delugeVPN writing to the cache taking up all the CPU resources, even pinning deluge to 4 specific cores doesnt help as it still uses all cores at 100%
My cache is a cache pool of 2 devices, one 960gb and one 250gb for a total of 1.2TB~
Heres disk/cpu activity with 0 torrents downloading to array/cache and around 20~ torrents uploading from array
Heres disk/cpu activity with 2 torrents downloading to cache capped at 30MB/s and around 20~ torrents uploading from array at around 9MB/s
Heres disk/cpu activity with 2 torrents downloading to cache capped at 10MB/s and around 20~ torrents uploading from array at around 9MB/s
is this expected behavior? like is my CPU too shit for my download speed? Why would writes to cache impact my CPU to this extent?
-
still not working admin/adminadmin on a fresh install restarted container, reinstalled it, etc.
not working and i cant find the user/pass in the appdata to change either
following frollays instructions doesnt help either
-
any idea why i would get this error?
dont think i've done any changes to this file personally.
It doesn't seem like the plugins respect the delay setting any longer, they will always auto update instantly.
Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/ca.update.applications/include/exec.php on line 100
-
i hadn't done any changes for a long time then 2 days ago or so delugeVPN just completely stopped downloading/uploading anything. If i turn VPN off in the template it starts downloading/uploading instantly. and the weird thing is even when VPN is active and DelugeVPN is not downloading anything, the privoxy proxy still works for clients connected to it.Any ideas? attached the (hopefully) relevant logedit: Started a new container with the same settings and it works, so something mustve gotten screwed up within the config
oh boy here i go troubleshootin againedit2: had to change incoming port for whatever reason... had been running fine for months and then just died, weird.
-
any idea on this one @binhex? 😁
On 1/21/2020 at 8:58 PM, MammothJerk said:I'm getting a lot of spam in my deluged.log with "Session status key not valid:" thanks to the stats plugin, it starts off during the plugin load as such:
20:19:41.892 [INFO ][deluge_label.core :78 ] *** Start Label plugin *** 20:19:41.907 [INFO ][deluge.pluginmanagerbase :189 ] Plugin Label enabled... 20:19:41.914 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:41.914 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:41.914 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:41.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:42.214 [INFO ][deluge.pluginmanagerbase :189 ] Plugin Stats enabled... 20:19:42.218 [INFO ][deluge.pluginmanagerbase :189 ] Plugin Scheduler enabled...then it starts repeating constantly after all my torrents have loaded
20:19:49.616 [INFO ][deluge.core.torrentmanager :885 ] Finished loading 2032 torrents in 0:00:03.984063 20:19:49.831 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:49.831 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:50.046 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:50.046 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:50.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:50.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:50.936 [INFO ][deluge.core.rpcserver :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. 20:19:51.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:51.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:52.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:52.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:53.138 [INFO ][deluge.core.rpcserver :171 ] Deluge Client connection made from: xxx.x.x.x:xxxxx 20:19:53.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:53.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:54.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:54.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:55.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:55.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:56.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:56.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:57.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:57.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:58.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:58.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:59.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:59.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:00.656 [INFO ][deluge.core.rpcserver :171 ] Deluge Client connection made from: xxx.xxx.x.xxx:xxxxx 20:20:00.749 [INFO ][deluge.core.rpcserver :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. 20:20:00.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:00.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:01.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:01.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:02.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:02.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:03.484 [INFO ][deluge.core.rpcserver :171 ] Deluge Client connection made from: xxx.xxx.x.xxx:xxxxx 20:20:03.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:03.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:04.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:04.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:05.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:05.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:06.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:06.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:07.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:07.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:08.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:08.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:09.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:09.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:10.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:10.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:11.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:11.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:12.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:12.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:13.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:13.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:14.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:14.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:15.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:15.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:16.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:16.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:17.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:17.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:18.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:18.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:19.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:19.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:20.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:20.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:21.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:21.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:22.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:22.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:23.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:23.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:24.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:24.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:25.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:55:09.531 [INFO ][deluge.pluginmanagerbase :250 ] Plugin Stats disabled... -no errors for 5 minutes til i start it up again 20:59:43.245 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:43.245 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:43.246 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:43.246 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:43.510 [INFO ][deluge.pluginmanagerbase :189 ] Plugin Stats enabled... 20:59:44.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:44.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:45.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:45.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:46.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:46.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:47.246 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:47.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:48.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:48.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connectionsDisabling the stats plugin prevents this spam from occurring, and according to this topic on the deluge bug tracker i have to do something to the stats egg. the problem is i'm not sure where this egg is located in the unraid/docker/delugevpn installation. any pointers on what to do to fix this?
[Plugin] NUT v2 - Network UPS Tools
in Plugin Support
Posted
I'm having an issue where UPS load is not updating at all. It starts out at 162W and sits there stuck even with load changes and parity checking etc. it never changes.
Any idea why i'm having this problem?
I would use the built-in unraid APC UPS plugin but that doesnt give me any info whatsoever, its just stuck when starting for some reason.