Ticket #314 (closed enhancement: fixed)

Opened 3 years ago

Last modified 2 years ago

options for status page (fase 1)

Reported by: robert Owned by: robert
Priority: major Milestone: MediaMosa 2.2
Component: Core Version:
Keywords: Cc:
MoSCoW: Must Have Estimated time after impact analysis:
Related to project: none Tested: no
Accepted: no Estimated Hours: 8

Description (last modified by MC-arjen) (diff)

Proposal:

The status page could be divided into four parts:

  • configuration settings
  • component status
  • server status
  • server working (only with unit-tests possible)

Configuration settings:

  • php settings (see above)
  • apache settings, test option for rewrite mod apache;
  • database settings (should-have innodb settings, buffer)
  • db schema correct?
  • privileges user correct?
  • toolset present? ffmpeg +version, lua, lua-lpeg, yamdi, MP4Box
  • ...

Component status

  • SANNAS: mount exists, structure ok, readwrite access. disk space free.
  • db: connection works ok? (measure lag)
  • authentication
  • rest interface works? (do a version call).
  • ftp server works
  • OAI service (if available)
  • transcoding server

Server monitoring

  • upload/download/app/job server present?
  • are vpcore versions on servers correct?
  • mount on all servers correct (except db)?

Server working
(These are unittests which must work in a sandbox, to not interfere with normal tables.)

  • download test
  • play ticket test
  • upload
  • job start (analyze file)
  • streaming of a video
  • authorization
  • authentication
  • still play

Proposed statuses: red (not working), yellow (working, but over a threshold), green (working), gray (unknown)

The first 3 types of tests go on the main status page, the last one on the unittest page.

Change History

Changed 3 years ago by Frans

  • moscow changed from Should Have to Must Have
  • milestone changed from MediaMosa X.X to MediaMosa 2.2

Changed 3 years ago by peter

Starten met een basisversie van 8 uur. Hier enkele tests die de omgeving testen. Later uitbreiden.

Changed 3 years ago by robert

  • estimated_hours set to 8

Changed 3 years ago by robert

  • summary changed from options for status page to options for status page (fase 1)

Changed 3 years ago by robert

Option to see your PHP upload settings;

* current max upload setting on your upload REST interface.
* Max possible setting on your upload REST interface (64bit will allow up to 16gb files POST upload, even 2TB might be possible, but that depends on your browser).
* Status of the upload REST interface (available, tests worked).
* URLs of your upload servers and their information.

Changed 3 years ago by MC-arjen

  • description modified (diff)

Changed 3 years ago by robert

  • owner set to forgacs
  • status changed from new to assigned

Changed 3 years ago by robert

  • owner changed from forgacs to robert

Changed 3 years ago by robert

  • status changed from assigned to closed
  • resolution set to fixed

Changed 3 years ago by Frans

  • status changed from closed to reopened
  • resolution fixed deleted

Questions:

1) Why do I see the yellow code below the Component Status page?

Database	Schemas. It doesn't check the foreign keys

mediamosa_user_favorite:
Current:
  "fav_id" varchar(32) NOT NULL COMMENT 'The name of group.',
Schema:
  "fav_id" varbinary(32) NOT NULL COMMENT 'The ID to the favorite object.',

etc...

2) Status Server shows some warnings:

    *  Warning: Invalid argument supplied for foreach() in _mediamosa_maintenance_status_server() (line 258 of /var/opt/www/vpcore/htdocs/sites/all/modules/mediamosa/maintenance/status/mediamosa_maintenance_status.module).
    * Warning: Invalid argument supplied for foreach() in _mediamosa_maintenance_status_server() (line 258 of /var/opt/www/vpcore/htdocs/sites/all/modules/mediamosa/maintenance/status/mediamosa_maintenance_status.module).
    * Warning: Invalid argument supplied for foreach() in _mediamosa_maintenance_status_server() (line 258 of /var/opt/www/vpcore/htdocs/sites/all/modules/mediamosa/maintenance/status/mediamosa_maintenance_status.module).

Changed 2 years ago by Frans

  • status changed from reopened to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.