Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHP Fatal error: Uncaught RuntimeException #2626

Open
scottia opened this issue Mar 14, 2019 · 13 comments
Open

PHP Fatal error: Uncaught RuntimeException #2626

scottia opened this issue Mar 14, 2019 · 13 comments

Comments

@scottia
Copy link

scottia commented Mar 14, 2019

Branch Dev

[14-Mar-2019 10:57:14 America/Chicago] PHP Fatal error: Uncaught RuntimeException in /var/www/nZEDb/libraries/mhor/php-mediainfo/src/Runner/MediaInfoCommandRunner.php:98
Stack trace:
#0 /var/www/nZEDb/libraries/mhor/php-mediainfo/src/MediaInfo.php(37): Mhor\MediaInfo\Runner\MediaInfoCommandRunner->run()
#1 /var/www/nZEDb/nzedb/processing/post/ProcessAdditional.php(2228): Mhor\MediaInfo\MediaInfo->getInfo('/var/www/nZEDb/...', false)
#2 /var/www/nZEDb/nzedb/processing/post/ProcessAdditional.php(2395): nzedb\processing\post\ProcessAdditional->getMediaInfo('/var/www/nZEDb/...')
#3 /var/www/nZEDb/nzedb/processing/post/ProcessAdditional.php(1369): nzedb\processing\post\ProcessAdditional->_processVideoFile('/var/www/nZEDb/...')
#4 /var/www/nZEDb/nzedb/processing/post/ProcessAdditional.php(760): nzedb\processing\post\ProcessAdditional->_processExtractedFiles()
#5 /var/www/nZEDb/nzedb/processing/post/ProcessAdditional.php(566): nzedb\processing\post\ProcessAdditional->_processReleases()
#6 /var/www/nZEDb/misc/update/nix/multiprocessing/.do_not_run/switch.php(248): nzedb\p in /var/www/nZEDb/libraries/mhor/php-mediainfo/src/Runner/MediaInfoCommandRunner.php on line 98

@niel
Copy link
Contributor

niel commented Mar 14, 2019

Is this frequent, or more of a one off?
I'll take a look, but there's not much I can do with that info except look for any obvious mistakes like typoes.

@scottia
Copy link
Author

scottia commented Mar 14, 2019

Yes, very frequent. Happens alot and fill up the logs many times a day. Over 2 or 3 days have a very large log file to delete.

@niel
Copy link
Contributor

niel commented Mar 15, 2019

OK, it should be a lot easier to get more info then. In particular the expanded version of the stack trace (the part hidden with ellipses above).

@scottia
Copy link
Author

scottia commented Mar 15, 2019

I don't think I can pull the expanded log, can I? If so, will do.

@niel
Copy link
Contributor

niel commented Mar 15, 2019

You might have to install x-debug and mess with its settings

@scottia
Copy link
Author

scottia commented Mar 26, 2019

Well I tried setting up x-debug and phpstorm but I can't figure out. That error will not go away and ends up freezing up zed.

@niel
Copy link
Contributor

niel commented Mar 26, 2019

You should only need X-Debug, and configure it so it gives expanded details. That will affect the logs too.

@scottia
Copy link
Author

scottia commented Mar 26, 2019

you have a simple way to run X-Debug for what you need. I've never used a debugger. X-Debug extension is installed and configured. I verified it but am not sure how to activate it or pull a log. That's why I was using phpstorm.

@niel
Copy link
Contributor

niel commented Mar 26, 2019

It's no different to what you were doing before. i.e. pasting that error log at the top of the post. Just now it should have more info in it if X-Debug is configured correctly ;-)
You'll probably have to read which options to add to x-debug's configuration though, I don't remember which ones off the top of my head.

@scottia
Copy link
Author

scottia commented Mar 26, 2019

I realized x-debug settings needed to be activated in ZED to run :)

It's running (and freezes) but not providing anymore info in PHP log that before. Will see what I have once it runs for awhile. Error is still occurring.

@scottia
Copy link
Author

scottia commented Mar 28, 2019

Same error. No extra X-Debug information.

[28-Mar-2019 09:01:58 America/Chicago] PHP Fatal error: Uncaught RuntimeException in /var/www/nZEDb/libraries/mhor/php-mediainfo/src/Runner/MediaInfoCommandRunner.php:98
Stack trace:
#0 /var/www/nZEDb/libraries/mhor/php-mediainfo/src/MediaInfo.php(37): Mhor\MediaInfo\Runner\MediaInfoCommandRunner->run()
#1 /var/www/nZEDb/nzedb/processing/post/ProcessAdditional.php(2228): Mhor\MediaInfo\MediaInfo->getInfo('/var/www/nZEDb/...', false)
#2 /var/www/nZEDb/nzedb/processing/post/ProcessAdditional.php(2395): nzedb\processing\post\ProcessAdditional->getMediaInfo('/var/www/nZEDb/...')
#3 /var/www/nZEDb/nzedb/processing/post/ProcessAdditional.php(1369): nzedb\processing\post\ProcessAdditional->_processVideoFile('/var/www/nZEDb/...')
#4 /var/www/nZEDb/nzedb/processing/post/ProcessAdditional.php(760): nzedb\processing\post\ProcessAdditional->_processExtractedFiles()
#5 /var/www/nZEDb/nzedb/processing/post/ProcessAdditional.php(566): nzedb\processing\post\ProcessAdditional->_processReleases()
#6 /var/www/nZEDb/misc/update/nix/multiprocessing/.do_not_run/switch.php(248): nzedb\p in /var/www/nZEDb/libraries/mhor/php-mediainfo/src/Runner/MediaInfoCommandRunner.php on line 98

@Bart39
Copy link
Contributor

Bart39 commented Mar 28, 2019

https://github.com/mhor/php-mediainfo/pull/83/files/462d8e9c630289ff4219285f10f7b3edac0026d1

Might be related - is one of the lines mentioned in your error

@niel
Copy link
Contributor

niel commented Apr 20, 2019

@scottia Makes sure that XDebug is actually being loaded. For CLI do:
php -m
to list modules.
For web create a file called test.php in the .../www directory containing only:
<?php phpinfo(); ?>
and got to localhost://test.php page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants