Jump to content

SUBIECTE NOI
« 1 / 5 »
RSS
Radio care se incinge

problema -amplificator cu tranzis...

Retragere bani din cont inainte d...

Plata cu cardu si bacsisu
 Primire bani din Danemarca prin N...

Alerta securitate Fedora Linux 40...

Problemuțe sistem audio ma&#...

Renovare balcon
 installation has failed there was...

Montura polara.....

Sfat inchiriere locuinta unei per...

Sursa stereo -> amplif mono
 Dan Blondu vs. Marian Piciu

Side - Antalya

Nume fetita - international dar c...

A fost lansat MX Linux 23.3
 

CentOS 5.5 - Crontab nu functioneaza

- - - - -
  • Please log in to reply
7 replies to this topic

#1
SINEKT

SINEKT

    Cyber-omul

  • Grup: Banned
  • Posts: 4,047
  • Înscris: 23.02.2007
Am un script de backup pus in crontab astfel:

4SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/

# run-parts
01 * * * * root run-parts /etc/cron.hourly
42 15 * * * root run-parts /etc/cron.daily
22 4 * * 0 root run-parts /etc/cron.weekly
42 4 1 * * root run-parts /etc/cron.monthly
55 09 * * * /scripts/backup


La un moment dat chiar functiona foarte bine, insa acum nu mai vrea de nici o culoare sa porneasca scriptul de backup. Scriptul in sine pornit separat cu ./backup din directorul scripts functioneaza cat se poate de bine, de la cap la coada. Cu ps -A vad crond ruland, este setat pe on in chkconfig, ce sa mai verific ?

Edited by SINEKT, 22 November 2011 - 10:31.


#2
mufa

mufa

    Porc misogin

  • Grup: Super Moderators
  • Posts: 40,804
  • Înscris: 13.01.2005

 SINEKT, on 22nd November 2011, 10:31, said:

ce sa mai verific ?
Logurile. :D

#3
SINEKT

SINEKT

    Cyber-omul

  • Grup: Banned
  • Posts: 4,047
  • Înscris: 23.02.2007
Ma, scuze ca raspund ca un mare incepator, dar am cautat si eu pe net pe unde gasesc logurile alea (presupun ca in /var/log) si acolo nu gasesc nimic niciodata cand am probleme, nici macar cea mai mica urma de aplicatiile in cauza prin loguri, nimic care sa ma ajute cat de putin. Nu ma uit unde trebuie sau care e faza ?

Uite ce zice logul cron:

Nov 20 16:01:01 server crond[29075]: (root) CMD (run-parts /etc/cron.hourly)
Nov 20 17:01:01 server crond[29173]: (root) CMD (run-parts /etc/cron.hourly)
Nov 20 18:01:01 server crond[29271]: (root) CMD (run-parts /etc/cron.hourly)
Nov 20 19:01:01 server crond[29370]: (root) CMD (run-parts /etc/cron.hourly)
Nov 20 20:01:01 server crond[29468]: (root) CMD (run-parts /etc/cron.hourly)
Nov 20 21:01:01 server crond[29566]: (root) CMD (run-parts /etc/cron.hourly)
Nov 20 22:01:01 server crond[29664]: (root) CMD (run-parts /etc/cron.hourly)
Nov 20 23:01:01 server crond[29762]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 00:01:01 server crond[29860]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 01:01:01 server crond[29958]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 02:01:01 server crond[30056]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 03:01:01 server crond[30155]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 04:01:01 server crond[30253]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 05:01:01 server crond[30351]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 06:01:01 server crond[30449]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 07:01:01 server crond[30547]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 08:01:01 server crond[30645]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 09:01:01 server crond[30743]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 10:01:01 server crond[31226]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 11:01:01 server crond[31664]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 12:01:01 server crond[32100]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 13:01:01 server crond[32198]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 14:01:01 server crond[32296]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 15:01:01 server crond[32394]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 15:42:01 server crond[32462]: (root) CMD (run-parts /etc/cron.daily)
Nov 21 15:42:01 server anacron[32468]: Updated timestamp for job `cron.daily' to 2011-11-21
Nov 21 16:01:01 server crond[523]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 17:01:01 server crond[705]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 18:01:01 server crond[803]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 19:01:01 server crond[902]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 20:01:01 server crond[1000]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 20:15:04 server crond[2247]: (CRON) STARTUP (V5.0)
Nov 21 20:20:01 server crond[2246]: (CRON) STARTUP (V5.0)
Nov 21 21:01:01 server crond[2400]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 22:01:01 server crond[2498]: (root) CMD (run-parts /etc/cron.hourly)
Nov 21 23:01:01 server crond[2596]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 00:01:01 server crond[2694]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 01:01:01 server crond[2792]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 02:01:01 server crond[2890]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 03:01:01 server crond[2988]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 04:01:01 server crond[3086]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 05:01:01 server crond[3184]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 06:01:01 server crond[3282]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 07:01:01 server crond[3380]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 08:01:01 server crond[3478]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 09:01:01 server crond[3576]: (root) CMD (run-parts /etc/cron.hourly)
Nov 22 09:47:17 server crontab[3686]: (root) BEGIN EDIT (root)
Nov 22 09:52:01 server crond[2246]: (*system*) RELOAD (/etc/crontab)
Nov 22 09:54:13 server crond[3723]: (CRON) STARTUP (V5.0)
Nov 22 10:01:01 server crond[3789]: (root) CMD (run-parts /etc/cron.hourly)

Nici urma de scriptul meu. Deci mai departe ce fac ?

Edited by SINEKT, 22 November 2011 - 10:53.


#4
SINEKT

SINEKT

    Cyber-omul

  • Grup: Banned
  • Posts: 4,047
  • Înscris: 23.02.2007
In primul post aveam 4SHELL=/bin/bash si am corectat in crontab in SHELL=/bin/bash si tot nu merge.

#5
Huza

Huza

    Senior Member

  • Grup: Senior Members
  • Posts: 2,417
  • Înscris: 07.11.2006
Drept de executie pe fisier ai?
Ai incercat un simplu echo "test" > fisier la fiecare X minute?
service crond restart

#6
SINEKT

SINEKT

    Cyber-omul

  • Grup: Banned
  • Posts: 4,047
  • Înscris: 23.02.2007

 Huza, on 22nd November 2011, 14:01, said:

Drept de executie pe fisier ai?
Da.

Quote

Ai incercat un simplu echo "test" > fisier la fiecare X minute?
Nu merge, nu se creeaza fisierul (* * * * * echo "test" > /test).

Quote

service crond restart
Dupa fiecare modificare in /etc/crontab. ;)

#7
SINEKT

SINEKT

    Cyber-omul

  • Grup: Banned
  • Posts: 4,047
  • Înscris: 23.02.2007
Am renuntat la linia suplimentara si am copiat scriptul meu in /etc/cron.daily. Acum merge. Multumesc de ajutor.

#8
MembruAnonim

MembruAnonim

    MembruAnonim

  • Grup: Banned
  • Posts: 399,715
  • Înscris: 08.10.2015

 SINEKT, on 22nd November 2011, 14:49, said:

Am renuntat la linia suplimentara si am copiat scriptul meu in /etc/cron.daily. Acum merge. Multumesc de ajutor.

crontab -e pentru a edita crontab-ul, in /var/spool/crontab/root o sa iti apara linia din cron care iti ruleaza scriptul. Eu asa fac de fiecare data cand vreu sa adaug ceva in cron. /etc/crontab nu l-am editat niciodata si nici nu stiu daca trebuie sa il editezi.

Anunturi

Neurochirurgie minim invazivă Neurochirurgie minim invazivă

"Primum non nocere" este ideea ce a deschis drumul medicinei spre minim invaziv.

Avansul tehnologic extraordinar din ultimele decenii a permis dezvoltarea tuturor domeniilor medicinei. Microscopul operator, neuronavigația, tehnicile anestezice avansate permit intervenții chirurgicale tot mai precise, tot mai sigure. Neurochirurgia minim invazivă, sau prin "gaura cheii", oferă pacienților posibilitatea de a se opera cu riscuri minime, fie ele neurologice, infecțioase, medicale sau estetice.

www.neurohope.ro

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Forumul Softpedia foloseste "cookies" pentru a imbunatati experienta utilizatorilor Accept
Pentru detalii si optiuni legate de cookies si datele personale, consultati Politica de utilizare cookies si Politica de confidentialitate