Remapping channel numbers

And I'm home all day today tinkering on some other tech projects so happy to test as much as you need. Thanks again!

nope, that looks like they're the same format...so that shouldn't be the issue. hmm...

any other ideas or possible solutions to try?

unfortunately no...i haven't seen this happen and i don't have a HDHR to test with to see if there's something weird going on there.

this weekend i'll try to see if i can reproduce the issue with a fake hdhr, but if that doesn't work i'm not sure what is causing this. are all of your TVE sources working correctly?

Is your HDHR one of the original "dual" models?

No I just bought it brand new just a few months ago just for Channels.

@crackers8199 all other TVE sources work fine. And their channel numbers will save. The HDHR channels work in the front end instance but they have the original channel numbers.

Quick question, I'm not super familiar with Docker Containers. Is there a way to remove the Front end Container and simply have access to the backend container & channel mapping system? I'd like to be able to install the front end on the bare metal and access the backend in the containers. I do a fair bit of trans-coding and the front end container is struggling a bit.

if i'm understanding what you're asking, yeah that should be possible. you just need to change where your front end is referencing to reference the mapper/backend container.

It's there something in your setup file that I can modify to stop it from creating the front end docker? Unless I'm misunderstanding, that is banking advertised on port 8089 for the host machine.

just remove the frontend parts from the docker compose file.

1 Like

Awesome. Thank you, I'll need with it. Is that the file you have us put the ip address in?

no, that's the .env file for laravel. the docker-compose file is the one that defines the entire stack (frontend/backend/mapper)...

1 Like

OK. Cool. Thank you sir.

1 Like

Update: it completely worked. I now have a non-docker front end that points to the backend docker channel remapping program! Thanks for the tips. Hopefullythe hardwarettranscoding will work better than software was when they were both insidethe containers.

1 Like

Hopping on here to ask another question.

I had to do a fresh install of my DVR PC due to some tinkering gone wrong. In resetting everything up, I've run into an error in regards to the PHP application. It's not running at all, just stuck in a restarting phase.

I pulled up the docker-compose logs, and this is what they said.

channels-mapper     | Starting Apache httpd web server: apache2.
channels-mapper     | Installing dependencies from lock file (including require-dev)
channels-mapper     | Verifying lock file contents can be installed on current platform.
channels-mapper     | Your lock file does not contain a compatible set of packages. Please run composer update.
channels-mapper     | 
channels-mapper     |   Problem 1
channels-mapper     |     - phpspec/prophecy is locked to version 1.12.1 and an update of this package was not requested.
channels-mapper     |     - phpspec/prophecy 1.12.1 requires php ^7.2 || ~8.0, <8.1 -> your php version (8.1.3) does not satisfy that requirement.
channels-mapper     |   Problem 2
channels-mapper     |     - phpspec/prophecy 1.12.1 requires php ^7.2 || ~8.0, <8.1 -> your php version (8.1.3) does not satisfy that requirement.
channels-mapper     |     - phpunit/phpunit 9.4.3 requires phpspec/prophecy ^1.12.1 -> satisfiable by phpspec/prophecy[1.12.1].
channels-mapper     |     - phpunit/phpunit is locked to version 9.4.3 and an update of this package was not requested.
channels-mapper     | 
channels-mapper     | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.2. Set the 'ServerName' directive globally to suppress this message

As mentioned prior, I'm not super familiar with Docker containers. Does the PHP version rely on the parent system's version control? How would I go about fixing this?

Any tips are much appreciated! Thanks!!!

i think the problem here is that the latest version of the apache-buster php image is using php 8.1, and phpspec/prophecy doesn't have an 8.1 release yet. we should be able to resolve this by telling it to use php 8.0.x instead.

try this: in the code mapper Dockerfile, change the top line from this...

FROM php:apache-buster

to this:

FROM php:8.0.16-apache-buster

and then rebuild everything.

8.0.16 is the latest 8.0.x version i could find a php apache-buster docker image for. i think this will work, let me know if you have any issues.

1 Like

That did the trick. Thank you very much.

1 Like

@crackers8199 Is it possible to run the mapper in a docker with pre-existing frontend AND backend?

I could use a bit of help getting this up and running on Windows 10. I put this aside a while ago because it was beyond me. Since then I have gained a bit more confidence with docker. I am having an issue and was wondering if anyone that has it up and running on Windows or @crackers8199 can point me in the right direction.
I have some success but then I see this:

Creating channels-backend   ... done
Creating channels-frontend  ... done
Creating channels-mapper    ... done
Creating channels-mapper-db ... done
Attaching to channels-frontend, channels-mapper-db, channels-backend, channels-mapper
channels-backend     | Running Channels DVR..
channels-frontend    | Running Channels DVR..
channels-mapper-db   | 2022-05-06 21:26:18+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.38-1debian10 started.
channels-mapper-db   | 2022-05-06 21:26:18+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
channels-mapper-db   | 2022-05-06 21:26:18+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.38-1debian10 started.
channels-mapper-db   | 2022-05-06 21:26:18+00:00 [Note] [Entrypoint]: Initializing database files
channels-mapper-db   | 2022-05-06T21:26:18.802328Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
channels-mapper-db   | 2022-05-06T21:26:19.103545Z 0 [Warning] InnoDB: New log files created, LSN=45790
channels-mapper-db   | 2022-05-06T21:26:19.179380Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
channels-mapper-db   | 2022-05-06T21:26:19.200677Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 2b452776-cd83-11ec-8902-0242ac140002.
channels-mapper-db   | 2022-05-06T21:26:19.206864Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
channels-mapper      | Starting Apache httpd web server: apache2AH00112: Warning: DocumentRoot [/var/www/html/public] does not exist
channels-mapper      | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.3. Set the 'ServerName' directive globally to suppress this message
channels-mapper-db   | 2022-05-06T21:26:19.924564Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
channels-mapper-db   | 2022-05-06T21:26:19.924627Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
channels-mapper-db   | 2022-05-06T21:26:19.925484Z 0 [Warning] CA certificate ca.pem is self signed.
channels-mapper-db   | 2022-05-06T21:26:19.954428Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
channels-mapper      | .
channels-mapper      | chmod: cannot access '/var/www/html/storage': No such file or directory
channels-mapper      | AH00112: Warning: DocumentRoot [/var/www/html/public] does not exist
channels-mapper      | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.3. Set the 'ServerName' directive globally to suppress this message
channels-mapper      | .
channels-mapper      | chmod: cannot access '/var/www/html/storage': No such file or directory
channels-mapper exited with code 1
channels-mapper      | AH00112: Warning: DocumentRoot [/var/www/html/public] does not exist
channels-mapper      | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.3. Set the 'ServerName' directive globally to suppress this message
channels-mapper-db   | 2022-05-06 21:26:23+00:00 [Note] [Entrypoint]: Database files initialized
channels-mapper-db   | 2022-05-06 21:26:23+00:00 [Note] [Entrypoint]: Starting temporary server
channels-mapper-db   | 2022-05-06 21:26:23+00:00 [Note] [Entrypoint]: Waiting for server startup
channels-mapper-db   | 2022-05-06T21:26:23.288747Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
channels-mapper-db   | 2022-05-06T21:26:23.290197Z 0 [Note] mysqld (mysqld 5.7.38) starting as process 78 ...
channels-mapper-db   | 2022-05-06T21:26:23.293890Z 0 [Note] InnoDB: PUNCH HOLE support available
channels-mapper-db   | 2022-05-06T21:26:23.293938Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
channels-mapper-db   | 2022-05-06T21:26:23.293945Z 0 [Note] InnoDB: Uses event mutexes
channels-mapper-db   | 2022-05-06T21:26:23.293950Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
channels-mapper-db   | 2022-05-06T21:26:23.293954Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
channels-mapper-db   | 2022-05-06T21:26:23.293958Z 0 [Note] InnoDB: Using Linux native AIO
channels-mapper-db   | 2022-05-06T21:26:23.294927Z 0 [Note] InnoDB: Number of pools: 1
channels-mapper-db   | 2022-05-06T21:26:23.295070Z 0 [Note] InnoDB: Using CPU crc32 instructions
channels-mapper-db   | 2022-05-06T21:26:23.297392Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
channels-mapper-db   | 2022-05-06T21:26:23.311682Z 0 [Note] InnoDB: Completed initialization of buffer pool
channels-mapper-db   | 2022-05-06T21:26:23.314940Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
channels-mapper-db   | 2022-05-06T21:26:23.327038Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
channels-mapper-db   | 2022-05-06T21:26:23.338163Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
channels-mapper-db   | 2022-05-06T21:26:23.338279Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
channels-mapper-db   | 2022-05-06T21:26:23.356913Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
channels-mapper-db   | 2022-05-06T21:26:23.357543Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
channels-mapper-db   | 2022-05-06T21:26:23.357585Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
channels-mapper-db   | 2022-05-06T21:26:23.359063Z 0 [Note] InnoDB: 5.7.38 started; log sequence number 2749976
channels-mapper-db   | 2022-05-06T21:26:23.359339Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
channels-mapper-db   | 2022-05-06T21:26:23.359547Z 0 [Note] Plugin 'FEDERATED' is disabled.
channels-mapper-db   | 2022-05-06T21:26:23.361931Z 0 [Note] InnoDB: Buffer pool(s) load completed at 220506 21:26:23
channels-mapper-db   | 2022-05-06T21:26:23.366589Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
channels-mapper-db   | 2022-05-06T21:26:23.366635Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
channels-mapper-db   | 2022-05-06T21:26:23.366643Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
channels-mapper-db   | 2022-05-06T21:26:23.366647Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
channels-mapper-db   | 2022-05-06T21:26:23.367300Z 0 [Warning] CA certificate ca.pem is self signed.
channels-mapper-db   | 2022-05-06T21:26:23.367404Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
channels-mapper-db   | 2022-05-06T21:26:23.371602Z 0 [Warning] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
channels-mapper-db   | 2022-05-06T21:26:23.383936Z 0 [Note] Event Scheduler: Loaded 0 events
channels-mapper-db   | 2022-05-06T21:26:23.384949Z 0 [Note] mysqld: ready for connections.
channels-mapper-db   | Version: '5.7.38'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  MySQL Community Server (GPL)
channels-mapper      | .
channels-mapper      | chmod: cannot access '/var/www/html/storage': No such file or directory
channels-mapper-db   | 2022-05-06 21:26:24+00:00 [Note] [Entrypoint]: Temporary server started.
channels-mapper exited with code 1
channels-mapper      | AH00112: Warning: DocumentRoot [/var/www/html/public] does not exist
channels-mapper      | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.3. Set the 'ServerName' directive globally to suppress this message
channels-mapper      | .
channels-mapper      | chmod: cannot access '/var/www/html/storage': No such file or directory
channels-mapper-db   | Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
channels-mapper-db   | Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
channels-mapper exited with code 1
channels-mapper      | AH00112: Warning: DocumentRoot [/var/www/html/public] does not exist
channels-mapper      | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.3. Set the 'ServerName' directive globally to suppress this message
channels-mapper      | .
channels-mapper      | chmod: cannot access '/var/www/html/storage': No such file or directory
channels-mapper exited with code 1

Keep getting these type of errors - Any help will be appreciated Thanks!

shouldn't be an issue, it just sits inbetween them and re-maps the channel numbers for you. you'd just need to modify the backend env var to fit your scenario.

1 Like