Mettbrot
-
Posts
418 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Mettbrot
-
-
Hi Marv,
thanks for your feedback! I thought it started on my machine ? I can look into the problem tomorrow and will report back!
-
7 hours ago, alturismo said:
here its located in /appdata/nextcloud
After a lot of digging I found out that the log file is not in /config but in /data which contains the cloud data. Dont know why it would be there but OK. This file revealed that the binloging format of the mariaDB was wrong. So I checked my custom.cnf but it contained that important binlogging_format=mixed line. It just did not accept my custom config at all!
Long story short: Your /mnt/cache/Apps/mariadb/custom.cnf must not be chmod 777 or alike but instead be 0644 for mariadb to accept it. Source: https://ubuntuforums.org/showthread.php?t=1811158 So be careful with the NewPrmission tool!
Problem solved!
-
I couldn't even find the nextcloud.log file anywhere? Where is it normally located?
On 27.10.2017 at 11:46 AM, Mettbrot said:Hey,
ever since the last round of updates I cannot logon my nextcloud server. When I log In using my admin username and password I get an "Internal Server Error"
QuoteThe server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log.
-
Just letting you know: I have updated tvheadend to the latest stable 4.2.4-10
-
Hey,
ever since the last round of updates I cannot logon my nextcloud server. When I log In using my admin username and password I get an "Internal Server Error"
QuoteThe server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log.
What can I do to solve this out? The only clue in the nginx error.log is this line about a missing favicon in nextcloud:
Quote2017/10/27 11:38:20 [error] 306#306: *180 open() "/config/www/nextcloud/favicon.ico" failed (2: No such file or directory), client: 172.17.0.1, server: _, request: "GET /favicon.ico HTTP/1.0", host: "192.168.178.39:444"
-
I guess you can only change values there if you disable tvheadend at the top. Play with disable enable a bit. I know it can be a bit tricky
While you're at it: Change the data directory to your cache drive. Something like: /mnt/cache/Apps/tvheadend
-
On the settings page there is a button "advanced configuration" where you can put in your superuser credentials. You can then add additional users through the tvheadend interface.
-
Glad it worked out!
Let me know if it works for you after enabling everything!
-
You can see the status of tvheadend if you go to your unraid settings > tvheadend. Is it running? Is everything detected ok on the left side (media tree, dvb adapter, password)?
-
1
-
-
This is the plugin version of tvheadend so I have no clue about the docker. I also never tried anything oscam related, maybe someone else can chip in on this one..
-
Hi,
I have a similar problem. Since a couple of weeks I cannot seem to stop the docker containers, leading to unraid hanging on shutdown. I tried to update one of the dockers when I noticed the issue:
After the download it said
stopping docker: error
removing image: error
starting docker: unable to start because a docker with the same name is running
/etc/rc.d/rc.docker stop is not running forever and shutdown does not work. I had to force shut down several times resulting in parity checks with up to 20 bad sectors.
I recently removed the docker image file and reset everything. But now I have those errors again.
Diagnostics are attached
-
Hello there,
recently, my system has become unstable and is not shutting down properly. It produces a kernel bug on shutdown and I have to force power it down resulting in parity sync issues. The attached pictures show the messages from shutdown until it halted.
There is also a diagnostics file attached. Please let me know if I can provide anything more.
I have the following things installed:
Docker: sabnzbd, sickrage, teamspeak3, letsencrypt, mariadb, nextcloud
tvheadend pluginno VMs running
-
I would also like this feature
On 1.7.2015 at 2:54 PM, bonienl said:You mean something like this ?
-
I just updated tvheadend in the plugin to the latest 4.2.3 stable version.
-
I can logout at the top right corner and login using any of the accounts specified as users in the webUI plus the super user. As far as I remember you can't logout when you are using the superuser because to the system you are not a regular user. It's kind of hacked into the UI I guess. I don't know how it works with asterisk users though.. sorry
-
Hi there!
its never wrong to ask
as far as I know the rights management inside tvheadend is very granular. You can select rights like EPG or DVR or live tv per user. If your wildcard user doesn't have a password and can access the epg i suppose you will be "logged in" without password with that user when you visit the web interface and can only see the epg. You may log out at the top right corner and use your super user or a user with admin rights to login like you said. For other questions you might want to check the help function inside the web interface or ask at the forum over at http://tvheadend.org Most of the time I am overwhelmed by all the functionality too.
You can access even more functionality if you set the settings level to expert in the top right corner.
As far as the wake up function goes, you have to put your actual configuration path into the command, for me it's would be like this:
/usr/local/emhttp/plugins/tvheadend/scripts/tvheadend_wakeup.sh "/mnt/user/Apps/tvheadend/dvr/log"The log files only exist if there is an actual timer scheduled, correct. The script gets executed when tvheadend is shut down. That would include a shutdown of the server
I hope I could help you. Don't hesitate to ask again if something's unclear. I will probably update the tvheadend version to the latest stable in mid-July.
-
Hi everyone!
I just took some time to update tvh to the latest 4.2.1 STABLE.
You read correctly, they finally released a stable version
I also fixed some problems with the dependencies, so the plugin should install correctly now - even on new installations! Please let me know if it doesn't!
Have fun!
-
Now that was fast! Great, thank you
-
I wsa going to try and setup ngnix and letsencrypt to reach nextcloud over the internet. How do I setup the ports? Does ngnix get ports 80 and 443 and what do I set nextcloud to? Seems like you have set it to 446 internally and nginix redirects there?
Maybe I shoud rather wait for this:
On 17.3.2017 at 5:15 PM, CHBMB said:I am working on a guide currently, hopefully will be published on the linuxserver.io website soon.
How is it coming along?
-
Did the USB device patch we talked about make it into this release?
-
10 hours ago, limetech said:
Yes the patch has made it's way to linux 'next' but not yet distributed to maintainers. The way it works is all changes are applied to 'next' first and tested. If it works there, then the patch is sent down to all the maintainers of the various stable releases. Probably a matter of days before this happens on this particular patch I would guess. So let's see what the next kernel point release brings us. If we're ready to generate our own point release and we haven't seen this patch yet, then I'll go ahead and put into our kernel.
great! Thank you for your ongoing support!!
-
3 hours ago, limetech said:
Can you provide link to that?
Sure, https://github.com/torvalds/linux/commit/43fab9793c1f44e665b4f98035a14942edf03ddc
I dont know how the versioning works on Linus' github though. I suppose this is only a mirror of the current development branch...
-
On 21.2.2017 at 6:05 PM, Mettbrot said:
@limetech I have scouted some of the bugtrackers that mention this issue. This seams to be the main one: https://bugzilla.kernel.org/show_bug.cgi?id=191891
another usb device: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853894
about an audio adapter: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852749
another (older) one here: https://bugzilla.kernel.org/show_bug.cgi?id=109521
same problem with a usb LAN controller: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852556
I found the following two patches:
https://patchwork.kernel.org/patch/9534751/
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852749 (this is the one about the audio adapter though)I hope this helps
I asked Marc on the Kernel Bugzilla if he tried the patch and it seems to work for him! The patch is also in the most recent linux kernel code on github, but I think its not included in the 4.9 release cycle anymore.. If you update the kernel in the next release could you include that patch? I dont think dvb-usb would harm anyone not willing to fiddle with dvb devices
-
On 19.2.2017 at 7:48 PM, limetech said:
We've been monitoring the kernel change logs for mention of this, but nothing has appeared yet. Have you seen anywhere someone has posted a patch?
@limetech I have scouted some of the bugtrackers that mention this issue. This seams to be the main one: https://bugzilla.kernel.org/show_bug.cgi?id=191891
another usb device: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853894
about an audio adapter: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852749
another (older) one here: https://bugzilla.kernel.org/show_bug.cgi?id=109521
same problem with a usb LAN controller: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852556
I found the following two patches:
https://patchwork.kernel.org/patch/9534751/
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852749 (this is the one about the audio adapter though)I hope this helps
-
2
-
unRAID OS version 6.4.0 Stable Release Available
in Announcements
Posted
Did you even read the first post? There is a note about exactly that in there under Secure Access...