Jump to content


Photo

4.1.1.0 Playback Errors - FreeNAS 11.2


  • Please log in to reply
50 replies to this topic

#41 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 131280 posts
  • Local time: 05:08 PM

Posted 11 June 2019 - 12:49 PM

I don't really have the time to beta test anything at the minute, and 4.1.1.0 is working pretty well for me so I don't have the need.

 

That said, I'd be completely confused if I did want to test things out, as the FreeBSD situation doesn't seem to get any clearer.

 

I gave up on plugins well before FreeNAS 11, so always build my own jail, and then ideally install the latest pkg.  This is what my current jail is running, and I assume the quarterly updates by default?

 

When I was testing the 3.6.x.x beta it was simply a case of updating emby from the github repository, but it doesn't look that straight forward anymore as dependancies need to be updated, and they might not depending on how you pkg.conf is setup?

 

I tried updating my jail to 4.2.0.14 using the pkg add github folder method, but ran into lots of problems with basis playback.  I upgraded the jail pkg and tried again, but it was no better.  Given a lack of time and plenty of snapshots, I rolled back to 4.1.1.0 and all is good again.

 

Its all a bit of a mess though, and there must be an easier way?

 

If you're not using freenas plugins, then you can use FreeBSD ports for stable, and the instructions on our website for beta:

 

https://emby.media/freebsd-server.html

 

Both are very easy methods. Thanks.



#42 MRobi OFFLINE  

MRobi

    Advanced Member

  • Members
  • 248 posts
  • Local time: 06:08 PM

Posted 11 June 2019 - 02:36 PM

If you're not using freenas plugins, then you can use FreeBSD ports for stable, and the instructions on our website for beta:

 

https://emby.media/freebsd-server.html

 

Both are very easy methods. Thanks.

Others may chime in here and correct me if I'm wrong, but I don't believe any of us in this thread have issues with not knowing how to install. We're all pretty comfortable with the various methods of installing.

 

What we're saying is that there's information lacking with each release to properly install, or in all of our cases here update to a newer version.

 

If some builds are built off of quarterly and others off of latest, how are we to know which to use when updating to a new version? 

When a new dependency such as libvpx is required, how are we to know until we update and run into issues?

 

All of the issues in this thread were run into while updating to a new version and were all related to package settings or dependencies. 

It would take 2 extra minutes to add "FREEBSD - Quarterly packages and new dependency XXXXX required" into the release notes and it would save a bunch of unnecessary topics and troubleshooting here.

 

I'm not even going to touch the topic of building from ports. I personally think the customization options offered when building from ports is going to result in a nightmare for anybody outside of the more advanced users.


  • Baenwort likes this

#43 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 131280 posts
  • Local time: 05:08 PM

Posted 11 June 2019 - 02:46 PM

I'll add that information to the website install instructions to clarify. Also i"ll be adding that the pkg install ... command for dependencies should be run with each update to ensure that you get any new dependencies that might have been added to the list.



#44 adrianwi OFFLINE  

adrianwi

    Advanced Member

  • Members
  • 338 posts
  • Local time: 10:08 PM
  • LocationScotland

Posted 11 June 2019 - 04:48 PM

Thanks for the response, which clarifies things a little, and the list of updated dependancies for each release will help even more.

 

I'd like to get to a situation where it was relatively easy to jump between stable and beta releases, which at the minute I'm struggling to see.  I could create two separate jails, but it would be easier not too and a better test if I'm using my full database.


Edited by adrianwi, 11 June 2019 - 04:48 PM.


#45 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 131280 posts
  • Local time: 05:08 PM

Posted 11 June 2019 - 04:55 PM

 

 

I'd like to get to a situation where it was relatively easy to jump between stable and beta releases

 

That's not something we suggest. Even if is easy from the install side of things, the newer version could create any number of changes. Then when you roll back, the older version might not be able to cope with those changes.



#46 adrianwi OFFLINE  

adrianwi

    Advanced Member

  • Members
  • 338 posts
  • Local time: 10:08 PM
  • LocationScotland

Posted 12 June 2019 - 05:41 AM

Sorry, my wording could have been clearer.  Only looking to jump from stable to beta in order to test something.  If I needed to go back to a stable release, I'd roll back a snapshot, and not try to downgrade the jail.



#47 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 131280 posts
  • Local time: 05:08 PM

Posted 12 June 2019 - 12:07 PM

Thanks for the feedback.

#48 PhilWhite OFFLINE  

PhilWhite

    Advanced Member

  • Members
  • 381 posts
  • Local time: 05:08 PM

Posted 16 June 2019 - 09:44 PM

Updated my jail running 4.0.2.0 to 4.1.1.0, added libvpx and forced a new file and got the exact same error as the original post. 

Switched this jail from quarterly to latest and refreshed the new file and it played.

 

So in summary, I've got 4.1.1.0 which needed to be on latest to work. and 4.2.0.10 which needed to be on quarterly to work.

@MRobi

 

I don't know if you recall all that you did, but I am on quarterly with the three (actually four, but three jails with emby) and just down-graded from 4.2.0.14 to 4.1.1.0 and got the same play error until I restarted the jail.  I also re-scanned all libraries and everything works fine with no play errors.  Do you know if you restarted the jail after updating your version?  I wonder if that might fix some encountered problems?



#49 MRobi OFFLINE  

MRobi

    Advanced Member

  • Members
  • 248 posts
  • Local time: 06:08 PM

Posted 17 June 2019 - 08:45 PM

@MRobi

 

I don't know if you recall all that you did, but I am on quarterly with the three (actually four, but three jails with emby) and just down-graded from 4.2.0.14 to 4.1.1.0 and got the same play error until I restarted the jail.  I also re-scanned all libraries and everything works fine with no play errors.  Do you know if you restarted the jail after updating your version?  I wonder if that might fix some encountered problems?

Yes, I had many times. 

I'd also recommend against downgrading as such as it could cause issues with some of the dependencies. The better method would be to roll your jail back to a previous snapshot with the older version. 



#50 PhilWhite OFFLINE  

PhilWhite

    Advanced Member

  • Members
  • 381 posts
  • Local time: 05:08 PM

Posted 18 June 2019 - 08:15 AM

Yes, I had many times. 

I'd also recommend against downgrading as such as it could cause issues with some of the dependencies. The better method would be to roll your jail back to a previous snapshot with the older version. 

I agree, but in this instance I had skipped over the stable version and had been using betas.  There were some weird quirks with 4.2.0.14 (reported by others in the testing area), so I decided to go back to a stable version.  Looks like I got away with it; I have been on the quarterly branch all along, though.



#51 MRobi OFFLINE  

MRobi

    Advanced Member

  • Members
  • 248 posts
  • Local time: 06:08 PM

Posted 18 June 2019 - 02:41 PM

I agree, but in this instance I had skipped over the stable version and had been using betas.  There were some weird quirks with 4.2.0.14 (reported by others in the testing area), so I decided to go back to a stable version.  Looks like I got away with it; I have been on the quarterly branch all along, though.

The large majority of my issues have been from quarterly/latest and different builds requiring different pkgs. Although now I'm scratching my head if you're on 4.1.1.0 working on quarterly, and my 4.1.1.0 caused issues until I switched to latest. All I know for certain is any issues I run into after upgrading to a new build, the pkg version will be my first troubleshooting step moving forward.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users