Dies ist eine mobil optimierte Seite, die schnell lädt. Wenn Sie die Seite ohne Optimierung laden möchten, dann klicken Sie auf diesen Text.

Update für IPC 11.5 erschienen

AW: Update für IPC 11.5 erschienen

Okay dann werde ich nämlich gcc wahrscheinlich in die benötigten Paket mit aufnehmen
 
AW: Update für IPC 11.5 erschienen

Ich habe eine problem beim Update

Erstelle SQLite3 Datenbank.. [ DONE ]
Erstelle/Pruefe SQLite3 Tabellen.. [ DONE ]
Uebertrage alte webif.db in neue SQLite3 Datenbank.. [ DONE ]
Syslog neustarten..Webserver neustarten..no listening sockets available, shutting down
Unable to open logs
[ FAIL ]
Abbruch

Was muss ich da bitte ändern das er das update fertig macht ... ich habe da wohl etwas ausgeschalten. (IPC Web Interface geht nicht ...Fehler: Verbindung fehlgeschlagen)

Danke für die Hilfe
 
AW: Update für IPC 11.5 erschienen

Ich denke, da stimmt was mit dem Netzwerk nicht.
was steht in /etc/network/interfaces?

MfG
 
AW: Update für IPC 11.5 erschienen

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
 
AW: Update für IPC 11.5 erschienen

Gerade gelesen. Das Streamboard ist gerade down, kann sein, das es daran liegt.
Du solltest eine statische IP vergeben.
Code:
[COLOR=#333333]# interfaces(5) file used by ifup(8) and ifdown(8)[/COLOR]
[COLOR=#333333]auto lo[/COLOR]
[COLOR=#333333]iface lo inet loopback[/COLOR]

[COLOR=#ff0000]auto eth0[/COLOR]
[COLOR=#333333]#iface eth0 dhcp[/COLOR]
[COLOR=#333333]iface eth0 [/COLOR][COLOR=#ff0000]static[/COLOR]
[COLOR=#ff0000]address 192.168.x.xxx
netmask 255.255.255.0
broadcast 192.168.x.255
gateway 192.168.x.1[/COLOR]
Die rot markierten Stellen entsprechend anpassen.

MfG
 
AW: Update für IPC 11.5 erschienen

Ja danke für den Tip. Aber das ist mein VPS Server und ich habe eine Dynamische IP Adesse. Da kann ich ja eine DNS Adresse eintragen oder ???

PS:Ich werde mal später das update nochmal probieren . Ich hoffe dann funkt das ...

- - - - - - - - - -

es kommt alles

IPC Installation (Update) / V11.5 21.11.2014 18:45
===============================================================================
EMU Konfiguration ist bereits vorhanden!
-------------------------------------------------------------------------------

EMU-Konfiguration beibehalten?
Dies sind: /var/etc/* und /var/keys/*

Die IPC-Konfiguration bleibt nur bei Update selber Versionsnummer erhalten!
Ansonsten sind IPC, Autostart und Jobs neu einzustellen.

Konfiguration beibehalten? (j/n):



Jetzt gehts los..


Jetzt gehts los..

Download.. (ipc-115.tgz) [ DONE ]
Cron wird beendet.. [ DONE ]
Sichern.. (-> /var/backups/ipc/forsetup_20141121_1846) [ DONE ]
Saeubern.. [ DONE ]
Entpacken.. [ DONE ]
EMU-Konfiguration wird wiederhergestellt.. [ DONE ]
IPC-Konfiguration wird wiederhergestellt.. [ DONE ]
Addons ermitteln..
Tempdir setzen.. [ DONE ]
Logfiles erstellen..


und dann

System ist: 32-Bit
CCcam ist: CCcam.x86
OScam ist: oscam.x86
NewCS ist: newcs.i686
Camd3 ist: camd3.x86
sBox ist: sbox.x86
OSEmu ist: OSEmu.x86

Erstelle SQLite3 Datenbank.. [ DONE ]
Erstelle/Pruefe SQLite3 Tabellen.. [ DONE ]
Uebertrage alte webif.db in neue SQLite3 Datenbank.. [ DONE ]
Syslog neustarten..Webserver neustarten..no listening sockets available, shutting down
Unable to open logs
[ FAIL ]
Abbruch
root@debian ~ >
schade
 
Zuletzt bearbeitet von einem Moderator:
AW: Update für IPC 11.5 erschienen

jo nein das mit der ip passt . Es ist so, ich habe die Logs ausgemacht. Und ich denke jetzt das es irgentwas mit apache2 zu tun hat. Und nachdem ich das nicht mehr hinbringe, dachte ich mir ich mache ein Update. Und ein paar tage später ist mir aufgefallen das ich das IPC nicht mehr erreiche . Oscam inteface mit der gleichen IP geht schon .( danke)
Dann dachte ich mir ich mache ein IPC Update und dann stellt er ja alles wieder auf Standart einstellung bis auf die Oscam die kann man ja sichern lassen...fragt ja die Console danach. Geht aber irgentwie nicht. Aber an der Ip liegt es sicher nicht. Aber kann es sein das er das update nicht machen kann weil ich die Logs ausgemacht habe ??
 
AW: Update für IPC 11.5 erschienen

Ich glau, da wirst Du auf al-x warten müssen.
Versuch mal mit IPdesServers/ipc aufs WebIf zu kommen. Hat sich in der ipc.cfg was geändert?
Code:
i cfg
sollte dann so aussehen
Code:
# IPC-Konfiguration                                                      V11.5
# =============================================================================
# ACHTUNG: Parameter immer zwischen Anfuehrungszeichen -> 'wert'


#WebIf Control anzeigen als:
# menue = eigener Menueeintrag
# hide = versteckt unter Home
# stay = immer sichtbar unter Home
 WEBIF_CON='hide'


#WebIf Menue in welchem Style anzeigen:
# new = neues design
# old = altes design
 WEBIF_MENUE='new'


#WebIf Logs Display Style (new/old)
# new = with grep
# old = without grep, each logfile an own button..
 WEBIF_LOGS='new'


#Website Benutzer und Kennwort (.htaccess)
[COLOR=#ff0000]# diese einstellung darf nicht leer sein sonst geht die website/webif nicht![/COLOR]
 HTTPUSER='XXXXXXX'
 HTTPPASS='YYYYYYYY'
.
.
.
.
MfG
 
AW: Update für IPC 11.5 erschienen

Ja schon klar, ich habe da auch was drinnen stehen eine user name und auch passwort. Ich bekomme es trotzdem nicht hin leider


oder muss ich ein UDP port freigeben für install von IPC ich habe ja eine Firewall am rennen. Die Oscam updates waren kein problem . Eventuell bei IPC update ???? Hat da jemand plan ob ich da die Firewall etwas freimachen muss wegen update ??!
 
Zuletzt bearbeitet:
AW: Update für IPC 11.5 erschienen

Sieht so aus, als wäre deine apache2 - Config verpfuscht.
Wie sieht denn der Inhalt von /etc/apache2/ports.conf aus
 
AW: Update für IPC 11.5 erschienen

# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See for detailed information about
# the directives and /usr/share/doc/apache2-common/README.Debian.gz about
# Debian specific hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `-- ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf.d
# | `-- *
# `-- sites-enabled
# `-- *
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
# together by including all remaining configuration files when starting up the
# web server.
#
# In order to avoid conflicts with backup files, the Include directive is
# adapted to ignore files that:
# - do not begin with a letter or number
# - contain a character that is neither letter nor number nor _-:.
# - contain .dpkg
#
# Yet we strongly suggest that all configuration files either end with a
# .conf or .load suffix in the file name. The next Debian release will
# ignore files not ending with .conf (or .load for mods-enabled).
#
# * ports.conf is always included from the main configuration file. It is
# supposed to determine listening ports for incoming connections, and which
# of these ports are used for name based virtual hosts.
#
# * Configuration files in the mods-enabled/ and sites-enabled/ directories
# contain particular configuration snippets which manage modules or virtual
# host configurations, respectively.
#
# They are activated by symlinking available configuration files from their
# respective *-available/ counterparts. These should be managed by using our
# helpers a2enmod/a2dismod, a2ensite/a2dissite. See
# their respective man pages for detailed information.
#
# * Configuration files in the conf.d directory are either provided by other
# packages or may be added by the local administrator. Local additions
# should start with local- or end with .local.conf to avoid name clashes. All
# files in conf.d are considered (excluding the exceptions noted above) by
# the Apache 2 web server.
#
# * The binary is called apache2. Due to the use of environment variables, in
# the default configuration, apache2 needs to be started/stopped with
# /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
# work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#LockFile ${APACHE_LOCK_DIR}/accept.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
#PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
#Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
#KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
#MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
#KeepAliveTimeout 5

##
## Server-Pool Size Regulation (MPM specific)
##

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
#<IfModule mpm_prefork_module>
# StartServers 5
# MinSpareServers 5
# MaxSpareServers 10
# MaxClients 150
# MaxRequestsPerChild 0
#</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadLimit: ThreadsPerChild can be changed to this maximum value during a
# graceful restart. ThreadLimit can only be changed by stopping
# and starting Apache.
# ThreadsPerChild: constant number of worker threads in each server process
# MaxClients: maximum number of simultaneous client connections
# MaxRequestsPerChild: maximum number of requests a server process serves
#<IfModule mpm_worker_module>
# StartServers 2
# MinSpareThreads 25
# MaxSpareThreads 75
# ThreadLimit 64
# ThreadsPerChild 25
# MaxClients 150
# MaxRequestsPerChild 0
#</IfModule>

# event MPM
# StartServers: initial number of server processes to start
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxClients: maximum number of simultaneous client connections
# MaxRequestsPerChild: maximum number of requests a server process serves
#<IfModule mpm_event_module>
# StartServers 2
# MinSpareThreads 25
# MaxSpareThreads 75
# ThreadLimit 64
# ThreadsPerChild 25
# MaxClients 150
# MaxRequestsPerChild 0
#</IfModule>

# These need to be set in /etc/apache2/envvars
#User ${APACHE_RUN_USER}
#Group ${APACHE_RUN_GROUP}

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#

#AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
#<Files ~ "^\.ht">
# Order allow,deny
# Deny from all
# Satisfy all
#</Files>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
# It is also possible to omit any default MIME type and let the
# client's browser guess an appropriate action instead. Typically the
# browser will decide based on the file's extension then. In cases
# where no good assumption can be made, letting the default MIME type
# unset is suggested instead of forcing the browser to accept
# incorrect metadata.
#
#DefaultType None


#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
#HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
#ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
#LogLevel warn

# Include module configuration:
#Include mods-enabled/*.load
#Include mods-enabled/*.conf

# Include list of ports to listen on and which to use for name based vhosts
#Include ports.conf

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
#LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
#LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
#LogFormat "%h %l %u %t \"%r\" %>s %O" common
#LogFormat "%{Referer}i -> %U" referer
#LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see the comments above for details.

# Include generic snippets of statements
#Include conf.d/

# Include the virtual host configurations:
#Include sites-enabled/
#Include httpd.conf
Include httpd.conf
 
Zuletzt bearbeitet von einem Moderator:
AW: Update für IPC 11.5 erschienen

Das ist die apache2.conf. Bitte die ports.conf
 
AW: Update für IPC 11.5 erschienen

Hätte ein Frage zu IPC -
Wenn ich IPC installiere, wird irgendwas eingestellt so das das Therminal in Farbe ist sowie, mit dem dir befehl der Inhalt eines Ordners mit Details angezeigt wird.
Wie kann ich das so machen ohne ipc zu installieren? Habe am Notebook noch Linux drauf um bisschen zu üben.

Danke
 
Für die Nutzung dieser Website sind Cookies erforderlich. Du musst diese akzeptieren, um die Website weiter nutzen zu können. Erfahre mehr…