colloqi / pisignage-server Goto Github PK

in releases 0.9.0 and later , After deploy only first slide keeps repeating /flashing until the node server is closed at command line.

Could you advice plese:

/home/hermes/pisignage-server/node_modules/socket.io/lib/store.js:35
Store.prototype.proto = EventEmitter.prototype;
^

TypeError: Cannot read property 'prototype' of undefined
at Object. (/home/hermes/pisignage-server/node_modules/socket.io/lib/store.js:35:41)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (/home/hermes/pisignage-server/node_modules/socket.io/lib/manager.js:16:13)
at Module._compile (module.js:571:32)

Hi!
I would like to try pisignage server, but when I start it with "node server.js", I've got the following error msg.

Could you tell me what happend?

Thanks for your help

The drag-and-drop works incorrectly when assets are filtered. If, for example, you drag the first asset from the filtered list into your playlist, when it drops you get the first asset from the unfiltered list. Clicking on the + button does work correctly however.

Before updating to 0.9 I used htpasswd to create different logins for users. After updating, even with credentials set in settings I am never presented with a login dialog. These credentials set here work to access players and for players to auth to server.

Any ideas?

Till we solve please refresh the browser after playlist changes

Please add Deploy All button under players,

npm ERR! code 1
npm ERR! Command failed: /usr/bin/git clone --depth=1 -q -b 0.9.x https://github.com/colloqi/socket.io.git /home/a                                                      dspl/.npm/_cacache/tmp/git-clone-e1818b9d
npm ERR! /home/adspl/.npm/_cacache/tmp/git-clone-e1818b9d/.git: Permission denied
npm ERR!

switching from deprecated-dialogue to master branch using git checkout,
Did git pull origin master
then npm install,
gives above error

switch backed to deprecated-dialogue brach and did npm install, server working.

When I start server with node server.js i get this error.Can someone please help me.

• After update if you do not see your groups, please change *
• change the uri variable to "mongodb://localhost/pisignage-dev"*
• in config/env/development.js and restart the server *

info - socket.io started
Express server listening on port 3000 in development mode
Reset isConnected for 0 players

•    system check passed               *
  

Downloading http://pisignage.com/releases/package.json
#Done
New version is available: 2.2.1
Downloading http://pisignage.com/releases/piimage2.2.1.zip
################################################################################
################################################################################
################################################################################
################################################################################
#########################################################################fs.js:1
37
throw new ERR_INVALID_CALLBACK();
^

TypeError [ERR_INVALID_CALLBACK]: Callback must be a function
at makeCallback (fs.js:137:11)
at Object.unlink (fs.js:936:14)
at ClientRequest. (C:\Users\SchoolAdmin\pisignage-server\app\cont
rollers\scheduler.js:25:12)
at ClientRequest.emit (events.js:182:13)
at Socket.socketErrorListener (_http_client.js:391:9)
at Socket.emit (events.js:182:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)

Under the option to "You can select additional Playlists for Scheduling/Advt purposes", you are limited to 10 options, and mine have filled up very quickly. I would like an option to be able to have a rule extend over several days of the week instead of checking individual days similar to the Google Calendar "repeat" option found here: image link

I need a playlist to play Sunday through Thursday, and a different one to run Friday and Saturday at various times on each one.

Audio out option, Analog or HDMI in group settings.

amixer cset numid=3 2 - HDMI
amixer cset numid=3 1 - Analog
amixer cset numid=3 0 - Auto

Trying to modify the "username at pisignage.com" field causes the server.js proces to fail on Windows, with the following errors:
(node:3164) DeprecationWarning: Mongoose: mpromise (mongoose's default promise library) is deprecated, plug in your own promise library instead: http://mongoosejs.com/docs/promises.html express deprecated req.param(name): Use req.params, req.body, or req.query instead app\controllers\groups.js:74:13 express deprecated req.param(name): Use req.params, req.body, or req.query instead app\controllers\players.js:203:13 express deprecated req.param(name): Use req.params, req.body, or req.query instead app\controllers\players.js:207:13 restarting server
also
(node:3512) DeprecationWarning: Mongoose: mpromise (mongoose's default promise library) is deprecated, plug in your own promise library instead: http://mongoosejs.com/docs/promises.html restarting server

How to add the calendar asset?

I have added my credentials in '/config/env/all.js'. and entered 'localhost:3000' as redirect_url. what is redirect_base_url?
in '/public/app/templates/gcal-popup.html' there is action 'api/gcal/authorize' which is not present so pointed the action to '/app/controllers/gcal-authorize.js'. But with no success. action always gives 404 error

Following install instructions exactly and came across an error during the npm install piece... this is from the npm_debug.log

4008 error Failed to parse json
4008 error Unexpected token t
4009 error File: /home/daniel/.npm/range-parser/1.0.2/package/package.json
4010 error Failed to parse package.json data.
4010 error package.json must be actual JSON, not just JavaScript.
4010 error
4010 error This is not a bug in npm.
4010 error Tell the package author to fix their package.json file. JSON.parse
4011 error System Linux 3.13.0-24-generic
4012 error command "/usr/bin/nodejs" "/usr/bin/npm" "install"
4013 error cwd /home/daniel/pisignage-server
4014 error node -v v0.10.25
4015 error npm -v 1.3.10
4016 error file /home/daniel/.npm/range-parser/1.0.2/package/package.json
4017 error code EJSONPARSE
4018 verbose exit [ 1, true ]

1- export of playlist with file names & durations, export in csv or xls
2- copy paste playlist to make new playlist
3- adding same content more than ones in playlist

Our client has one of their players behind an HTTP proxy, which was configured on raspbian based on the answer here.

This player is not seen by the server and doesn't receive updates.

Is there anything I'm missing for this setup to work ?

reoccurring 'corrupt log file: (1507129200000.log)'

how to correct?

numbering to asserts in playlist to make the arrangement easy
or a up down arrow near asserts to pull down or up.
Drag up down of assets in playlist is ok if few assets in playlist
for larger playlist above two options will be helpful.

We noticed on our cluster of Pis that even if we check the ' Change at the end
of current cycle' checkbox before clicking deploy, the change is immediate across all Pis and does not wait for the cycle to end.

I have a local http stream, that is running fine in other raspbery pi's that are currently using Kodi. I am now trying using pisignage, which will use omxplayer. Where can i change omxplayer settings/flags in order to improve stream quality? Do you now tips about this?

I have created a pisignage-sever inside a virtual machine (running inside OpenStack infrastructure) that has its own private ip private subnet.
Then I have 1 raspberry pi installed with the latest player version, with a private ip address from a VLAN I specifically created for this situation. In order to establish communication between these devices I created firewall rules inside my routers, and both server and RPi can talk to each other. As obvious the server wont detect the RPi, so there is some way to add the player to the server?

We needed several different accounts for accessing the server web interface. PiSignage supports only one, so we used another way to do this. But it would be nice to support multiple accounts in PiSignage.

The work-around: We used our nginx reverse proxy to control access with basic auth. On success, we send the 'Authorization' header with the piSignage credentials to pisignage-server.

I've installed onto CentOS 6.7 as per instructions and got as far as

"node server.js"

I see it download latest release, and it says #done. I can also see that it is listening on TCP port 3000 (I can also telnet to this port from another host.

There is never any response on port 3000 though. Borwser just hangs there.

I've never used mongoDB before... On CentOS, data dir seems to be in var, so I changed this to /data/db..... I can now see '/data/db/pisignage-dev.ns' files

Can we have server.js give more clues? or can anyone advise where I should look next?

Can you help me? i run error

see attached image.

'unable to find/delete thumbnail: Error: ENOENT: no such file or directory, unlink '/home/pi/media/_thumbnails/halloween-ghouls.mp4.png'

when i navigate to the '/_thumbnails' folder there are 2-4 numbers before the filename it mentions in the terminal. EX: 8831_halloween-ghouls.mp4.png

I installed pignage local, i run into the following error:
When i post a file to /api/files i see the error below. I have an basic authentication header and form-data withe type file and a file.

Error: Unexpected field
at makeError (/home/vagrant/pisignage-server/node_modules/multer/lib/make-error.js:12:13)
at wrappedFileFilter (/home/vagrant/pisignage-server/node_modules/multer/index.js:39:19)
at Busboy. (/home/vagrant/pisignage-server/node_modules/multer/lib/make-middleware.js:112:7)
at Busboy.emit (events.js:106:17)
at Busboy.emit (/home/vagrant/pisignage-server/node_modules/multer/node_modules/busboy/lib/main.js:31:35)
at PartStream. (/home/vagrant/pisignage-server/node_modules/multer/node_modules/busboy/lib/types/multipart.js:213:13)
at PartStream.emit (events.js:95:17)
at HeaderParser. (/home/vagrant/pisignage-server/node_modules/multer/node_modules/busboy/node_modules/dicer/lib/Dicer.js:51:16)
at HeaderParser.emit (events.js:95:17)
at HeaderParser._finish (/home/vagrant/pisignage-server/node_modules/multer/node_modules/busboy/node_modules/dicer/lib/HeaderParser.js:68:8)
at SBMH. (/home/vagrant/pisignage-server/node_modules/multer/node_modules/busboy/node_modules/dicer/lib/HeaderParser.js:40:12)
at SBMH.emit (events.js:106:17)
at SBMH._sbmh_feed (/home/vagrant/pisignage-server/node_modules/multer/node_modules/busboy/node_modules/dicer/node_modules/streamsearch/lib/sbmh.js:159:14)
at SBMH.push (/home/vagrant/pisignage-server/node_modules/multer/node_modules/busboy/node_modules/dicer/node_modules/streamsearch/lib/sbmh.js:56:14)
at HeaderParser.push (/home/vagrant/pisignage-server/node_modules/multer/node_modules/busboy/node_modules/dicer/lib/HeaderParser.js:46:19)
at Dicer._oninfo (/home/vagrant/pisignage-server/node_modules/multer/node_modules/busboy/node_modules/dicer/lib/Dicer.js:197:25)

The 'stretch images to fit screen' option under players->group->group settings does not have any effect on assets with an image url. It only appears to work for images directly uploaded to the pi. I am using a 1795x937 .png image in a web page with no other elements, attempting to push to a 1920x1080 screen. The the image retains its size and does not fill the screen. The server is version 0.9.0, and the pi is version 1.8.5.